IssueTracker

Look, I know it's hard to build a platform like this, I know it's not trivial and it takes a lot of man hours but I'm starting to dread developing consumer apps for Android. I can barely build any app on my laptop (machine specs attached) without rendering my machine completely useless, cpu cores are locked up to 100% for as long as the build is taking place. Even my high end iMac 5K with the best configurable hardware and 24Gb ram has troubles when I'm building after a clean or even if it decides to do a almost-full build (or indexing for that matter). It's really frustrating. Why not limiting the process to some lower prio? Is it possible to max out the utilisation to ~90% instead of leaving it as it is right now?

Now you'll ask me to try Instant Run and I'll answer it right away, it's even worse when using Instant Run, so let's not go there.

This thing has been reported to death, logs have been given by a lot of developers.... this report is more out of frustration than anything else. I'm here sitting with my laptop and I can't even type on this ticket while my app is building. I'm free to give you more information but I'll probably not offer you anything else that has been reported/shared already.

Thanks for reading and for all you do on the Android tools.

Studio Build:
Version of Gradle Plugin: Doesn't matter, happens on every version since the first Alpha release at I/O 2013. But I use 1.5.0 on my production machine
Version of Gradle: Same as the above, doesn't really matter. Used all of the Gradle releases since the first A/S release. Currently on 2.12.
Version of Java: 7 and 8
OS: OSX, Mavericks, Yosemite and now El Capitan

Steps to Reproduce: Build an app