Comments (1)
Can you tell us more about what you perceive as a source of the overhead? We know about sequential dependency resolution, and will address this soon. Is the I/O in general a problem? Do you expect the machine to have enough memory to temporarily hold the cached state if needed?
The store
operation is an essential step to prepare for the execution phase, to allow parallel task execution, for example. It doesn't really happen at the end of the build. Our end goal is to get rid of non-configuration-cached execution, so falling back to it won't be a long-term solution.
An alternative solution could be to fail the build if the cached state cannot be reused to indicate that cache-priming build has to be re-run. Does this behavior fit your use case?
from gradle.
Related Issues (20)
- Gradle 8.8 crashed on MacOS 11.x (8.7 still works as expected) HOT 15
- https://docs.gradle.org/8.8/javadoc/package-list is HTTP/404 but HTTP/200 with 8.7 dokka requires to download this resource HOT 2
- Gradle 8.8 crash on MAC OS HOT 2
- Publish Gradle API
- Instrumentation doesn't intercept calls to super methods
- Publish latest commit included in the nightly build HOT 1
- Discourage or deprecate detached configurations HOT 6
- CachingTaskInputFileCollection loose relative path sensitivity
- Create release notes for the new Java compiler integration with the Problems API
- Wrong information about removing unintentional subprojects HOT 3
- Formatting should be the same with JDK8 compiler reports as with other compilers HOT 1
- Allow configurations to be safely resolved from outside of owning scope HOT 1
- Gradle 7+ "force" changes cause a different resolution behavior HOT 3
- Deprecate running Gradle on JVM versions < 17
- Add mechanism for different package managers to contribute their installed JVM toolchains HOT 2
- Task dependency inference doesn't work for named domain object containers HOT 1
- Idea plugin is not IP compatible when configured directly
- `unreportedProblemInCurrentCall` error when using configure action
- Allow Configuration Cache for TAPI requests without Isolated Projects HOT 1
- Problem description copied from the CC report is noisy and ill-formatted HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gradle.