Have the memory requirements changed between 8.9 a...
# community-support
t
Have the memory requirements changed between 8.9 and 8.10.1? I get quite a few "daemon disappeared unexpectedly" in CI stages where I have never before seen those and the infrastructure where these stages run on are identical. Anybody else noticed something? These are my JVM args:
org.gradle.jvmargs=-Dfile.encoding=UTF-8 -XX:+UseParallelGC -XX:SoftRefLRUPolicyMSPerMB=1 -XX:ReservedCodeCacheSize=512m -XX:+UnlockExperimentalVMOptions -Xmx8g -Xms8g -XX:MetaspaceSize=1g
p
it is not recommended to update to 8.10.1 for now https://gradle-community.slack.com/archives/CJWG8VDM0/p1725962479192089?thread_ts=1725886297.238689&cid=CJWG8VDM0 btw, I think gradle daemon is not recommended on cloud CI (where agents don't stay after finishing a build)
v
You practically always nowadays use a daemon, whether you use
--no-daemon
or not as the CLI VM is almost never suitable as daemon JVM. The difference is just whether an existing daemon will be reused or not, and whether it will survive the build or be quit at the end of the build. And if you have ephemeral CI agents, it should not really make that much of a difference whether Gradle will quit the daemon itself or whether the CI agent will just be gone and with it the remaining daemon.
Also that the Userguide recommended not to use the daemon on CI is long past. In the Gradle 3-4 userguides it was recommended to disable the daemon on CI. In the Gradle 5-8 userguides on the other hand it is recommended to enable the daemon on CI.
👍 1
❤️ 1
p
oh I must have read the outdate doc