With project isolation, will configuration cache w...
# configuration-cache
n
With project isolation, will configuration cache writing/reading be done in parallel too?
v
https://docs.gradle.org/current/userguide/isolated_projects.html says:
This allows configuration and tooling model creation for each project to safely run in parallel, with the result cached and invalidated independently for each project.
So I'd say yes, the goal is that configuration for multiple projects runs in parallel and even is stored to CC individually per project, so if one project's CC state is outdated all others could still be reused and only that project's configuration needs to be done.
n
Yeah the docs aren’t very clear on this but fingers crossed 🤞
v
Are they not?
n
It only says it's cached per project, not that it's stored per project. It's still possible that storing will be deferred until all projects are configured and they are stored in one, non parallelized job
v
Oh, I see what you mean. Whether configuration of one project can be persisted if configuration of the other fails.
Then I have no idea.
n
The reason I'm asking is that storing and loading has become very slow with large runs due to the number of modules in our project
Storing/loading them per project in parallel would be a huge win
3