You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
org.gradle.daemon.idletimeout is the same if there is 1 daemon running or if there are 10 daemons running
Expected Behavior
Provide two timeout options:
When daemon is the only daemon running on the machine (last daemon)
When there are other daemons still running
Context
I'm currently working on a project that creates very memory intensive gradle daemons - three "full" daemons running simultaneously would completely starve my 32GB system of all memory.
Most of the time this is not an issue - I'm only running one daemon that handles all the builds (my "main" daemon). But occasionally, I will start multiple gradle tasks simultaneously, which will create extra daemons. After this, there will be multiple daemons sitting in the background, hogging lots of memory, even though I only need one most of the time.
I workaround this issue by setting aggressively low org.gradle.daemon.idletimeout. This ensures extra daemons are terminated quickly and do not hog memory. But the problem is that this also means my main daemon will terminate quickly and thus making my main builds slower.
Solution I envision is to have separate timeout for my "main" daemon and for the extra daemons. So I could set aggressive timeout for the extra daemons, but still have my "main" daemon running for longer amounts of time.
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.
Current Behavior
org.gradle.daemon.idletimeout
is the same if there is 1 daemon running or if there are 10 daemons runningExpected Behavior
Provide two timeout options:
Context
I'm currently working on a project that creates very memory intensive gradle daemons - three "full" daemons running simultaneously would completely starve my 32GB system of all memory.
Most of the time this is not an issue - I'm only running one daemon that handles all the builds (my "main" daemon). But occasionally, I will start multiple gradle tasks simultaneously, which will create extra daemons. After this, there will be multiple daemons sitting in the background, hogging lots of memory, even though I only need one most of the time.
I workaround this issue by setting aggressively low
org.gradle.daemon.idletimeout
. This ensures extra daemons are terminated quickly and do not hog memory. But the problem is that this also means my main daemon will terminate quickly and thus making my main builds slower.Solution I envision is to have separate timeout for my "main" daemon and for the extra daemons. So I could set aggressive timeout for the extra daemons, but still have my "main" daemon running for longer amounts of time.
Somewhat related to the #14741
The text was updated successfully, but these errors were encountered: