A daemon is a computer program that runs as a background process, rather than being under the direct control of an interactive user.
The Gradle Daemon is a background process that does the heavy lifting of running builds, then stays alive between builds waiting for the next build. This allows data and code that is likely to be required in the next build to be kept in memory, ready to go. This dramatically improves the performance of subsequent builds. Enabling the Gradle Daemon is an extremely cheap way to decrease build times.
It is strongly recommended that the Gradle Daemon be enabled on all developer machines. It is recommend to not enable the Daemon for Continuous Integration and build server environments (see Section 18.3, “When should I not use the Gradle Daemon?”).
Gradle manages the Daemon automatically. If the build environment is configured to leverage the Daemon, Gradle will automatically start a Daemon process if none are available, or use any existing compatible daemons that are not currently busy. If a Daemon process has not been used for 3 hours, it will terminate itself. Once a development environment is configured to use the Daemon, it is typically transparent and able to be forgotten about.
--no-daemon command line switches enable and disable usage of the Daemon for individual build invocations when using the Gradle command line interface.
Typically, it is more convenient to enable the Daemon for an environment (e.g. a user account) so that all builds use the Daemon without requiring to remember to supply the
There are two recommended ways to enable the Daemon persistently for an environment:
Via environment variables - add the flag
-Dorg.gradle.daemon=true to the
GRADLE_OPTS environment variable
Via properties file - add
org.gradle.daemon=true to the
«GRADLE_USER_HOME» defaults to
«USER_HOME» is the home directory of the current user.
This location can be configured via the
--gradle-user-home command line switches,
as well as by the
GRADLE_USER_HOME environment variable and
org.gradle.user.home JVM system property.
Both approaches have the same effect.
Which one to use is up to personal preference.
Most Gradle users choose the second option and add the entry to the user
On Windows, this command will enable the Daemon for the current user:
(if not exist "%HOMEPATH%/.gradle" mkdir "%HOMEPATH%/.gradle") && (echo foo >> "%HOMEPATH%/.gradle/gradle.properties")
On UNIX-like operating systems, the following Bash shell command will enable the Daemon for the current user:
touch ~/.gradle/gradle.properties && echo "org.gradle.daemon=true" >> ~/.gradle/gradle.properties
Once the Daemon is enabled for a build environment in this way, all builds will implicitly use a Daemon.
The Gradle Daemon is not enabled by default. However, once it is enabled it is sometimes desirable to disable for some projects or for some build invocations.
--no-daemon command line switch can be used to force that a Daemon not be used for that build.
This is rarely used, but can sometimes be useful when debugging issues with certain builds or Gradle plugins.
This command line switch has the highest precedence when considering the build environment.
Gradle may emit a warning at the end of the build suggesting that you use the Gradle Daemon.
To avoid this warning you can enable the Daemon via the methods above, or explicitly disable the Daemon.
You can explicitly disable the Daemon by using the
--no-daemon command line switch as described above,
or use one of the methods for enabling the daemon mentioned above but using a value of
false for the
org.gradle.daemon property instead of
As it is not recommend to use the Daemon for Continuous Integration builds, Gradle will not emit the message if the
CI environment variable is present.
There are several reasons why Gradle will create a new Daemon, instead of using one that is already running. A new Daemon will be started if there are no idle, compatible, Daemons.
An idle Daemon is one that is not currently executing a build or doing other useful work.
A compatible Daemon is one that can (or can be made to) meet the requirements of the requested build environment. The Java installation to use to run the build is an example of an aspect of the build environment. Required JVM system properties for the build runtime is another example.
Some aspects of the requested build environment may not be able to be met by an already running Java process.
If the Daemon is running with a Java 7 runtime, but the requested environment calls for Java 8 then the Daemon is not compatible and another must be started.
Moreover, certain properties of a Java runtime cannot be changed once the JVM has started.
It is not possible to change the memory allocation (e.g.
-Xmx1024m), default text encoding, default locale, etc of a running JVM.
The “requested build environment” is typically constructed implicitly from aspects of the build client’s (e.g. Gradle command line client, IDE etc.) environment and explicitly via command line switches and settings. See Chapter 19, The Build Environment for details on how to specify and control the build environment.
The following JVM system properties are effectively immutable. If the requested build environment requires any of these properties, with a different value than a Daemon’s JVM has for this property, the Daemon is not compatible.
The following JVM attributes, controlled by startup arguments, are also effectively immutable. The corresponding attributes of the requested build environment and the Daemon’s environment must match exactly in order for a Daemon to be compatible.
The required Gradle version is another aspect of the requested build environment. Daemon processes are coupled to a specific Gradle runtime. Working on multiple Gradle projects during a session that use different Gradle versions is a common reason for having more than one running Daemon process.
If the requested build environment does not specify a maximum heap size, the Daemon will use up to 1GB of heap. It will use your the JVM's default minimum heap size. 1GB is more than enough for most builds. Larger builds with hundreds of subprojects, lots of configuration, and source code may require, or perform better, with more memory.
To increase the amount of memory the Daemon can use, specify the appropriate flags as part of the requested build environment. Please see Chapter 19, The Build Environment for details.
Daemon processes will automatically terminate themselves after 3 hours of inactivity.
If you wish to stop a Daemon process before this, you can either kill the process via your operating system or run the
gradle --stop command.
--stop switch causes Gradle to request that all running Daemon processes, of the same Gradle version used to run the command, terminate themselves.
Considerable engineering effort has gone into making the Daemon robust, transparent and unobtrusive during day to day development. However, Daemon processes can occasionally be corrupted or exhausted. A Gradle build executes arbitrary code from multiple sources. While Gradle itself is designed for and heavily tested with the Daemon, user build scripts and third party plugins can destabilize the Daemon process through defects such as memory leaks or global state corruption.
It is also possible to destabilize the Daemon (and build environment in general) by running builds that do not release resources correctly. This is a particularly poignant problem when using Microsoft Windows as it is less forgiving of programs that fail to close files after reading or writing.
If it is suspected that the Daemon process has become unstable, it can simply be killed.
Recall that the
--no-daemon switch can be specified for a build to prevent use of the Daemon.
This can be useful to diagnose whether or not the Daemon is actually the culprit of a problem.
It is recommended that the Daemon is used in all developer environments. It is recommend to not enable the Daemon for Continuous Integration and build server environments.
The Daemon enables faster builds, which is particularly important when a human is sitting in front of the build. For CI builds, stability and predictability is of utmost importance. Using a fresh runtime (i.e. process) for each build is more reliable as the runtime is completely isolated from previous builds.
The Gradle Tooling API (see Chapter 62, Embedding Gradle), that is used by IDEs and other tools to integrate with Gradle, always use the Gradle Daemon to execute builds. If you are executing Gradle builds from within you're IDE you are using the Gradle Daemon and do not need to enable it for your environment.
However, unless you have explicitly enabled the Gradle Daemon for you environment your builds from the command line will not use the Gradle Daemon.
The Gradle Daemon is a long lived build process. In between builds it waits idly for the next build. This has the obvious benefit of only requiring Gradle to be loaded into memory once for multiple builds, as opposed to once for each build. This in itself is a significant performance optimization, but that's not where it stops.
A significant part of the story for modern JVM performance is runtime code optimization. For example, HotSpot (the JVM implementation provided by Oracle and used as the basis of OpenJDK) applies optimization to code while it is running. The optimization is progressive and not instantaneous. That is, the code is progressively optimized during execution which means that subsequent builds can be faster purely due to this optimization process. Experiments with HotSpot have shown that it takes somewhere between 5 and 10 builds for optimization to stabilize. The difference in perceived build time between the first build and the 10th for a Daemon can be quite dramatic.
The Daemon also allows more effective in memory caching across builds. For example, the classes needed by the build (e.g. plugins, build scripts) can be held in memory between builds. Similarly, Gradle can maintain in-memory caches of build data such as the hashes of task inputs and outputs, used for incremental building.
Currently, the Daemon makes builds faster by effectively supporting in memory caching and by the JVM optimizer making the code faster. In future Gradle versions, the Daemon will become even smarter and perform work preemptively. It could, for example, start downloading dependencies immediately after the build script has been edited under the assumption that the build is about to be run and the newly changed or added dependencies will be required.
There are many other ways in that the Gradle Daemon will enable even faster builds in future Gradle versions.