How to optimise/control "loading projects" time?

Help/Discuss
1

in Build Scan it says this cannot be controlled and is a function of the number of projects in the build but this appears to be the dominant cost when faced with a configuration cache miss (in my current setup, ~40s loading and ~8s configuring).

Is there any way to understand what contributes to this cost? It seems awfully high.

2

Run through the gradle-profiler?

3

thanks, that has provided enough of a clue to try out some things (as the problem seems to be somewhat related to Gradle Action does not reuse configuration cache due git file has been removed. · Issue #30213 · gradle/gradle · GitHub)

1 Like