# State of the Configuration Cache - On the Road to Gradle 9

DevFeed: [State of the Configuration Cache - On the Road to Gradle 9](<https://devfeed.tech/articles/state-of-the-configuration-cache-on-the-road-to-gradle-9-24687.md>)

Original publisher: [Read original article](<https://blog.gradle.org/road-to-configuration-cache>)

Author: Mikhail Lopatkin

Published: 2025-03-14T04:00:00Z

Content type: article

Language: en

Sources: [The Gradle Blog](<https://devfeed.tech/sources/the-gradle-blog.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [build performance](<https://devfeed.tech/topics/build-performance.md>), [Caching](<https://devfeed.tech/topics/caching.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [caching](<https://devfeed.tech/tags/caching.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [incremental](<https://devfeed.tech/tags/incremental.md>), [performance](<https://devfeed.tech/tags/performance.md>)

## AI overview

This article explains the state of Gradle's Configuration Cache ahead of Gradle 9.0. It describes how the feature reduces repeated configuration-phase work, improves build performance and developer experience, and is planned to become the preferred execution mode before being enabled by default in Gradle 10.0.

## Source excerpt

Introduction As Gradle 9.0 approaches, we're sharing updates on the Configuration Cache--a key feature that significantly improves configuration time for large projects. In this major release, we plan to make the Configuration Cache the preferred execution mode, with the goal of enabling it by default in Gradle 10.0. The Configuration Cache is one of Gradle's most anticipated features; progress has been substantial. As Gradle Fellow Tony Robalik noted: "I'm excited about all the work Gradle has done to make the Configuration Cache stable and the preferred mechanism for running builds. At work, we've observed that enabling Configuration Cache globally will recover roughly 4 years of lost engineering time annually. The configuration cache also lays the foundation for Isolated Projects, which has been an eagerly awaited feature since Gradle first announced it several years ago!". Read this post to learn more about recent Configuration Cache performance and compatibility improvements, how to adopt it, and our plans for future releases. A Bit of History Development often happens in small increments--you write some code, run tests, fix failures, and repeat. In a build tool, this means executing the same tasks repeatedly. Gradle's execution model consists of three phases: Initialization - Discovers the project structure. Configuration - Builds the task graph. Execution - Runs tasks to perform the actual work. In an incremental workflow, where the same tasks are requested without changes to the build scripts, the configuration phase typically produces an identical task graph each time. Gradle excels at build caching, which caches the execution phase. This allows even massive projects and mono repositories to build in just a few seconds when no significant changes occur. However, generating the task graph for a complex project during the configuration phase can take a non-trivial amount of time. In some cases--like the project shown in the screenshot below--this overhead may eve