Does anyone know how to diagnose performance probl...
# compose-desktop
s
Does anyone know how to diagnose performance problems on Compose Desktop? I’m getting poor performance in one of my composables. I re-wrote it and it got dramatically better. Is there a way for me to figure out where compose is spending its time? Profiling was pretty useless.
blob shrug 1
a
What about adding print statements to different composables to see which one is getting recomposed?
s
Did that. Doesn’t really work well. 😞
m
Do you use and analyze output of
Copy code
kotlinOptions.freeCompilerArgs += listOf(
        "-P", "plugin:androidx.compose.compiler.plugins.kotlin:metricsDestination=/a/path",
        "-P", "plugin:androidx.compose.compiler.plugins.kotlin:reportsDestination=/a/path")
a
What didn't work? It's quite annoying but should be good enough to detect recompositions. If it's an open source project I can try to give it a look, if it's not then if you can share some details of the issue it may be enough, just in case I've faced a similar issue