I seem to recall some discussion on the arch call within the last few
months of a Java profiler that integrates with Eclipse and is free or
very cheap, at least for Eclipse committers. I might be confusing
myself with our discussion of UI testing software, though.
What's our current best practice, for profiling Eclipse components
(e.g., JDT)? I only need to run on JDK 1.6, and I want to look both at
heap usage and at hot spots in code execution. Should I be using TPTP,
or is there something else that is easier or better? YourKit,
JProfiler, ...?