Using JProfiler on Gradle tests.

Gradle starts lots and lots of threads and does random stuff.

If youre ever in the fortunate position of needing to trace down a Java performance bug, its alot of fun to use JProfiler to do so.

Here's how I did it on a project with a complex build.

The tricky part is to pick the right thread.

Make sure YOUR TEST IS ACTUALLY RUNNING when you grab the thread.



It will be the newest thread in the window:

 Not ready yet !

... Here we go...  grab the new guy.

Then, pick your settings, make sure to preserve the VM after the test completes. 

Later you can drill into things, and see where the most CPU is getting used up. 

Yay!