What could be the reason for this huge white gap b...
# gradle
p
What could be the reason for this huge white gap between the configuration and the execution phase?
t
Gradle transformations or building project model
p
Is there any way to analyze what's happening there?
t
what are the numbers in performance -> configuration tab?
v
p
message has been deleted
Ah that's the non execution step in the chart?
t
seems yes - "model configuration"
p
And if I was to publish my precompiled plugins I'd only cut it by the 9.8 secs?
👌 1
Ah if all this just wouldn't happen single threaded 🙈
If I split my precomp plugin into multiple precomp plugins they'd still all run single threaded right?
t
configuration phase right now is always single threaded. I suppose you want to improve CI time?
p
Also local speed
We have lots of code generating steps in the plugins and whenever we change anything there we have to rebuild the universe
And that stats above are from a maxed out macbook, with the other machines it's way worse
n
The configuration phase is single threaded but the included builds are not single threaded if they have the
org.gradle.parallel=true
flag.
p
Ah that's good insight. And is it possible to let a an included build depend on a regular module?
I want to come into a situation where a simple change in one of the code generating plugins doesn't cause a full recompilation of everything
u
Isnt script compilation & model building done only once anyways?
n
is it possible to let a an included build depend on a regular module
I'm not sure. What happens when you try it? I think they would be treated as two separate builds and be compiled twice.
Isnt script compilation & model building done only once anyways?
Correct. Script compilation is done once for a given buildscript classpath and cached. Model building is done once per build.