Gradle Configuration Cache: 2x faster, 4x smaller, and ready for Gradle 9.0

If you use Gradle Build Tool, then you probably know that each build includes a configuration phase that evaluates the build scripts of all participating projects and creates a task graph for requested tasks. In large codebases, this configuration time can be a significant part of the build—even longer than the execution phase—which disrupts developer flow and productivity. What if we could cache the configuration result for reuse in later builds? Gradle Configuration Cache offers exactly this. It's a popular feature that will become the preferred method of execution in Gradle 9.0. For Java/Kotlin, Android, or native projects, it can drastically improve configuration times by 2X and reduce cache size by 4X—especially valuable for builds cold-starting on CI. Join Alex Semin, Staff Software Engineer at Gradle, for a presentation on the current state of Configuration Cache: its benefits, functionality, value, and recent improvements in performance, resource use, and developer experience.