Post

I collaborated with @zacsweers.dev (who did most of the heavy lifting) to add automatic tracing for Graph bindings generated by Metro. If you are using DI, then you should be cognizant of it's costs. Metro automatically adds traces for all generated bindings when you enable Runtime tracing.

zacsweers.github.ioPerformance - MetroA multiplatform dependency injection framework for Kotlin

Rahul Ravikumar

@rahulrav.com

It was a really fun collaboration for me. @zacsweers.dev might feel differently perhaps 😅 I have never worked on Kotlin compiler plugins but Metro's codebase was pretty nice to work with. github.com/ZacSweers/me...

github.comAdd runtime tracing (#2354) · ZacSweers/metro@292c7a8Co-authored-by: Zac Sweers <pandanomic@gmail.com>

24/6/26, 5:40 am0 reposts3 likes

Rahul Ravikumar

@rahulrav.com

24 June

This feature builds on androidx.tracing 2.0, and therefore you can bring your own tracing backend if you like and even go as far as getting sampled traces from production.

Marcin Robaczyński

@scana-nananana.bsky.social

24 June

Hey Rahul, are `tracing-perfetto` and `tracing-perfetto-binary` releases for 2.0.0-alpha09 planned? Release notes here are a bit misleading suggesting that all artifacts with that version are available: developer.android.com/jetpack/andr...

developer.android.comTracing | Jetpack | Android Developers

Rahul Ravikumar

@rahulrav.com

24 June

No. Both those artifacts are effectively being replaced by tracing and tracing:wire. Compose will also officially move to the new Tracing APIs once we go beta.