Gradle Daemon

Gradle runs on the Java Virtual Machine (JVM) and uses several supporting libraries that require a non-trivial initialization time. As a result, it can sometimes seem a little slow to start. The solution to this problem is the Gradle Daemon: a long-lived background process that executes your builds much more quickly than would otherwise be the case. We accomplish this by avoiding the expensive bootstrapping process as well as leveraging caching, by keeping data about your project in memory. Running Gradle builds with the Daemon is no different than without. Simply configure whether you want to use it or not - everything else is handled transparently by Gradle.

1 Why the Gradle Daemon is important for performance

The Gradle Daemon is enabled by default starting with Gradle 3.0, so you don't have to do anything to benefit from it.

2 Running Daemon Status

To get a list of running Gradle Daemons and their statuses use the --status command.

3 Disabling the Daemon

Add the line

org.gradle.daemon=false

to /home/<username> (Linux)

4 Stopping an existing Daemon

gradle --stop

If you have the Java Development Kit (JDK) installed, you can easily verify that a Daemon has stopped by running the jps command