Essentially it seems that building kotlin based projects (e.g. Kotlin, kotlinx-coroutines) takes considerably longer on the cluster than on my local machine (whether building within the diagnostic container or directly). For example kotlinx-coroutines takes ~1hr while on my machine it takes ~few minutes.
Experimenting with setting that to 2 (which I think means 2 CPU versus the current of 30% of one CPU) dropping the kotlinx-coroutines down to ~10min versus 1hr :
This somewhat relates to https://github.com/apheleia-project/jbs-issues/issues/11 and is also mentioned in my doc
Essentially it seems that building kotlin based projects (e.g. Kotlin, kotlinx-coroutines) takes considerably longer on the cluster than on my local machine (whether building within the diagnostic container or directly). For example kotlinx-coroutines takes ~1hr while on my machine it takes ~few minutes.
I see that we set the CPU as follows:
This ends up in the yaml as (after my experimental change):
Tracing back through the history it has always been 300m ( cc @stuartwdouglas )
Background in
Experimenting with setting that to 2 (which I think means 2 CPU versus the current of 30% of one CPU) dropping the kotlinx-coroutines down to ~10min versus 1hr :