I need to profile a Swing app, fast. I don't have the time for a big learning curve, just need something that works out of the box, intuitively. TPTP (a.k.a Hayades) does not seem to do that, it throws exceptions and its info does not come across to me as self-explanatory. OK, it helped me find the method that is the biggest offender, but I've sort of knew that... though the method does not calculate much on its own, it delegates to a 3rd party library, why did not TPTP show that? So now what, how do I do even higher granularity than that?
Should I stick to TPTP, or is there a simpler solution?
Strange, it shows that the biggest offender is MyClass.access$1(MyClass), but MyClass does not have the word "access" anywhere, nor does it have any method that takes MyClass as an argument. No object weaving I hope, as it's not a persistent entity, a Swing class. What's going on?
I agree with Ernest. Check your MyClass and its inner classes - when a MyClass.InnerClass accesses Myclass's private member, compiler generates an additional method to access that member (it can't be accessed directly). Best way to improve performance is to make the field default (package) access.
Thanks for the info! That's very valuable. Now, back to the profiler question... any way to profile under Eclipse with higher granularity and without crashing all the time? And with less learning curve than TPTP?
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop