How Gradle Works: Inside the Daemon

Tue, 14 Mar 2023 11:27:52 +0000

Previously in the How Gradle Worksseries:

How Gradle Works: Startup

This is the second article of the series How Gradle Works.

In this article, we’ll explain what happens inside the Gradle Daemon JVM.

Why Do We Need Gradle Daemon?

In the last article , we mentioned that Gradle starts a Gradle Daemon JVM (“the daemon”) to run the build.

The userguide explains why we need the daemon.

The Daemon is a long-lived background process that reduces the time it takes to run a build. The Daemon reduces build times by caching project information across builds, running in the background so every Gradle build doesn’t have to wait for JVM startup, benefiting from continuous runtime optimization in the JVM, and watching the file system to calculate exactly what needs to be rebuilt before you run a build.

How Gradle Works: Startup

Thu, 09 Feb 2023 08:45:57 +0000

This is the first article of a series How Gradle Works, which includes the following topics:

How Gradle starts up
How many JVMs are involved in a Gradle build
What happens in each JVM during the build

We’ll explain the first topic How Gradle Starts Up in this blog.

Before reading on, we assume you are familiar with basic JVM/Gradle concepts (jar, classpath, wrapper, daemon, project, task, etc.).

How Gradle Starts Up

There are many ways to start a Gradle build:

Bo Zhang on foojay.io - Friends of OpenJDK

How Gradle Works: Inside the Daemon

Why Do We Need Gradle Daemon?

How Gradle Works: Startup

How Gradle Starts Up