From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I'm using the Gradle profiler to look into some performance issues, and when I run it using the defaults (i.e. the Tooling API), it uses a massive amount of RAM, much more than when I run it using `--cli`. Is that expected?

maybe? probably? what's massive? also I haven't used the gradle profiler... but "massive" seems like a hard question for people to answer

We'll I couldn't tell you exactly how much. It eats through all of my 64gb of RAM before getting killed :sweat_smile:

are you profiling gradle or your "jvm" app

I would except increased usage, but I'm not certain if I would expect more than double, but maybe depending on what profiler does

I mean they do tend to track multiple points of individual objects

yeah, I've never profiled gradle itself, so I don't know

but if your gradle instance itself is using many G that by itself sounds wrong

In this case that's correct, it's a rather large project.

have you tried getting java flight recorder set up to watch the gradle process? it might be lighter

yeah, even a large project, I wouldn't expect it ... just my opinion

I believe there's 24 workers getting spun up, and I set the Xmx to 8GB

the Xmx of gradle or the compiler/executor process

I'm betting you set that on the wrong thing :wink:

for gradle itself this is what I have

```org.gradle.caching=true
org.gradle.parallel=true
org.gradle.configuration-cache=true
org.gradle.configuration-cache.parallel=true
dependency.analysis.print.build.health=true
org.gradle.dependency.verification.console=verbose
org.gradle.jvmargs=-XX:+UseZGC \
  -XX:+ZGenerational \
  -XX:+UseStringDeduplication \
  -Xmx2g \
  -XX:MaxMetaspaceSize=768m \
  -Dfile.encoding=UTF-8 \
  -Duser.country=US \
  -Duser.language=en```