Mikhail Lopatkin

Lead Software Engineer at Gradle

Before joining the Gradle Build Tool team, Mikhail worked on several large-scale Android projects for over 10 years: from customizing phone firmware for one of the largest OEMs to building and maintaining a successful Chromium-based browser with millions of installs. After discovering his passion for improving development tooling, Mikhail made it his full-time job and has been working on improving Gradle’s Configuration Cache for the last four years.

Speeding up inner dev loop with Gradle Configuration Cache

Developers want their inner loop to be fast: code, test, repeat. With Gradle, there are no extra steps—you run the test, and it takes care of the rest, whether you’re tweaking a single line of code or upgrading all your dependencies. Gradle’s Configuration Cache is a feature that can significantly speed up the dev loop but its adoption might pose challenges. In this Session we'll walk through the most common hurdles, and learn how the Configuration Cache works. We’ll cover how to migrate gradually to get performance benefits early and how to maximize them later on. Key takeaways: - For those new to Configuration Cache - learn about a new way to speed up the development loop with Gradle - For those already familiar with it - learn about new developments and improvements - Everyone: learn how Configuration Cache works by example - Everyone: learn how to get the most out of Configuration Cache - Everyone: get a collection of recipes for common problems

Gradle Configuration Cache Office Hours

Following up on the Gradle Configuration Cache session, you can join Mikhail and Alex for an office hours session dedicated to helping you walk through the most common hurdles, and learn how the Configuration Cache works. We’ll help you understand how to migrate gradually to get performance benefits early and how to maximize them later on. Trying to enable Configuration Cache in your own project before the office hours may be helpful to get examples of concrete issues you'll be particularly interested in. Bring your Configuration Cache report with you!