Following Antoniossss’ advice I got in touch with a developer. As it turns out, Gradle is in fact quite resource hungry. Even for a simple “Hello World” application the daemon might use very well up to 150 MB and maybe even more. It is also alright, that multiple daemon threads are started, as long as … Read more
IntelliJ interacts with Gradle via the Gradle tooling API, which always uses the daemon. i.e. There is no way to turn it off. What you could do (after filing a bug report) is not to use the IntelliJ Gradle integration but instead generate IntelliJ project files with gradle idea
Under linux you may use pkill: pkill -f ‘.*GradleDaemon.*’ Under windows you may use wmic: WMIC PROCESS where “Name like ‘java%’ AND CommandLine like ‘%GradleDaemon%'” Call Terminate PS. Why “no scripting” when it is probably the easiest solution?
Update from June 25, 2017 At Google IO 2017 there was some updates about this topic. It’s not recommended anymore to set the flag on the dexOptions, so if you have something like the next, you can delete it. dexOptions { javaMaxHeapSize “2g” } Source: Speeding Up Your Android Gradle Builds Original answer: Android Studio … Read more