I know this is not a Gradle issue but Windows and macOS are not smart enough to just not giving Gradle all the CPU and blocking the rest of tools of being usable... Running

./gradlew build

in the terminal and getting IDEA/AS totally frozen during seconds or minutes is really annoying. Is there a workaround to just limit Gradle to use 90% CPU usage or something similar?

What I know folks typically do is reducing the amount of parallelism Gradle is allowed to do: •

--max-workers=2

on command line or •

org.gradle.workers.max=2

in gradle.properties (in your Gradle user home to have it for any Gradle invocation)

I will try this but I think I have already tried it in the past and still getting the IDE frozen.

you could try

--priority low

(or in `gradle.properties`:

org.gradle.priority=low

)

I had similar problems on windows, and I recommend applying both of those solutions in your user

gradle.properties

. javac since version 11 is using more than one core, so the gradle default of using all available cores (even counting E-cores on newer Intel) for the number of executors might be be a little high now. My setting is at half the number of (logical) P-cores, which works quite well for me.