I recently need to figure out where my application was spending the bulk of its time. I had thought that parallizing a process would help to increase performance, but before commiting to this path, I want to dig into the application and find the methods that were taking the most time. I’d used profiling in NetBeans before and it was the only thing I was running NetBeans for. Now that I’m using Eclipse (for Java only) I wanted to find an integrated solution.
While this solution isn’t integrated, it is installed on OS X, and I can launch it right from Eclipse and get the same profiling as NetBeans without switching environments.