Why You Should Enable Gradle Configuration Cache
summary
Gradle configuration cache (introduced as stable in Gradle 8.1) is explained: what made it hard to implement, how it works, and the surprising build-time performance gains it can deliver. The talk gives practical insights to help decide whether to enable configuration cache in your builds and includes links to the Gradle open-source codebase for contributors.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:30Speaker background
- 3:19Talk goals and structure
- 6:14Gradle build phases
- 9:24Gradle config phase problem
- 14:47Configuration Cache Report
- 16:36Task serialization
- 26:57How cache works
- 28:43Demo of benefits
- 32:21Load After Store idea
- 36:38Build lifecycle
- 37:44Future of config cache
- 39:07Q&A
related talks
11mInterview of Louis Jacomet
41mSpeeding up Jenkins, Gradle, and Maven with a Build Cache
36mTop Build Performance issues in Android projects - 2023 Edition
28mMaking the most of your Gradle Builds
49mGradle
43mSqueezing the last drop of performance out of your Gradle builds (en)
02h 49mGradle: Give Your Build Some Love and It Will Love You Back!
19mGetting to a green build with caching on CI