I've tested the 1.9.0's k2 compiler on our code ba...

# k2-adopters

[Cies]

I've tested the 1.9.0's k2 compiler on our code base and from the tests i did it seems that it all-just-works. The allWarningsAsErrors flag is on and needs to be on, this prevents me from really moving this fwd to production (just to test it). Also the compilation speed seems to be slower than for the old compiler, 3m05s to 3:29s, but i always find it hard to measure compile speed given all layers in the solution do caching and my system could also be using more resources and skew the results. use-fast-jar-file-system makes things some 10s of seconds slower (in a very small "n" benchmark). Our codebase has a lot of kotlinx-html templates that make use of the kotlin's eDSL feature (not sure that's the reason, but could explain the difference compared to measurements in other code bases).

[semoro]

Could you please share the build scan so we can take a look?
FastJarFS switch usually affects projects with small modules where the size of the classpath is more significant than the module itself. (Most modules take less than 1s to compile)

[Cies]

Are you interested in fast-jar speed? Or phrased better: what build scans would you be interested in receiving?

[semoro]

I’m interested why fast-jar fs performs worse than original implementation.
Also, it is interesting to see lines per second / total lines values for your build.

[Cies]

so I make 2 scans, both w/o k2, one for a regular build and one for a regular build with use-fast-jar-file-system enabled. right?

[semoro]

Right, thank you! 🙂

[Cies]

There were sent by private msg.