hey folks, I've finally gotten the slack android r...
# k2-adopters
z
hey folks, I've finally gotten the slack android repo to a benchmarkable state with K2 and unfortunately it does not look good for performance. The TL;DR is it's ~17% slower for us. Going to continue working through a few scenarios (this one is a non-abi kotlin change to a low-level subproject that should be pretty IC-friendly). But definitely feeling surprised right now
👀 1
🤦‍♂️ 1
t
With which Kotlin version are you testing? Is it KMP project?
z
2.0.0-RC1, not a KMP project. Mostly android-heavy project with ~850 subprojects
t
would be helpful if you could share Kotlin build metrics report in json format + Gradle build scan for RC1
and does project uses KAPT?
z
Will try to collect them. It does use kapt but in only 3-4 subprojects
g
I think Slack uses compile plugins a lot, at least Anvil. Maybe it also affects compilation time Also a case for us, so curious about this
z
Anvil runs almost entirely via KSP now. The only compiler plugin we run from it is IR merging, in the same projects that run kapt
g
But KSP is also a compiler plugin, isn't it?
z
KSP2 is not
👍 1
But fair KSP 1 still is
But it’s running in its own task too
👍 1
e
@Zac Sweers hey! Just wondering if you've managed to understand what was/is going wrong on the K2 side
z
No. Results seem to vary widely across repos
🥲 1