While I couldn’t compile our entire project with t...

# jvm-ir-backend-feedback

[elihart]

While I couldn’t compile our entire project with the ir backend (due to the crash above ^), I was able to compile a decent chunk of it and profiled the build with the gradle profiler. The ir backend seemed to give a solid 10% overall build speed improvement compared to vanilla 1.4.30. I hadn’t seen any mention of build speed improvements for android/jvm from the ir backend yet, so this was a pleasant surprise.

[elihart]

Considering that this is for the entire build, which includes many other android compilation tasks beyond just kotlin (plus lots of kapt work), it is pretty impressive that the new ir is able to have such a big impact

[udalov]

I don't want to downplay it, but are you sure the measurement is correct? Kotlin Gradle plugin uses a compiler daemon that is warming up after each run, so to test its performance correctly, one needs to stop the daemon (not the Gradle daemon, but the Kotlin compiler daemon) before measurement and preferably also run a few warming up rounds... I'm not familiar with gradle-profiler at all though, maybe it does exactly that for Kotlin builds? (sorry for my ignorance)

[elihart]

the tool is https://github.com/gradle/gradle-profiler

it does several warm up iterations, and then 10 measured iterations that are averaged. I don’t know that it stops the kotlin daemon, but I think it is a very standard tool for profiling gradle builds, and it has support for kotlin incremental builds.

Anyway, this tool shows substantially faster builds for each measurement using the ir backend