December 08, 2005
I'm using JProfiler 4.1.2 to profile and find things like memory leaks in the ObjectGrid thats about to ship. It's working very well. I'm using it to test ObjectGrid with JDKs for 1.4.2 and 1.5 from Sun and IBM.
I was tracking down a memory leak today and heres a tip. It's worth nulling out references to unused objects if you can because it makes reading heap profiles A LOT easier. Fewer things to see and wade through. I couldn't find my leak today until I added some code to 'destroy' objects when I'd done with them. Destroy meaning assign null to references to other objects when I'm done with the object. Once, I'd done this then it was easy to spot the leak. I'd imagine it doesn't hurt your GC times either.
As usual, I think it's still one of the best profilers on the market and for the money, hard to beat. My only gripe is no AIX support.
December 8, 2005 | Permalink
Billy, you should tell your colleagues that are working on Eclipse TPTP how the real profiler should look like...
Posted by: eu | Dec 9, 2005 6:31:50 PM
Any profiling tool is useful, even raw hprof. Although the early WSAD/RAD profiler had some performance issues of its own, the latest TPTP is actually quite snappy.
I've used it's predecessor, LiveJinsight, for many years in over 150 customer "situations". The unique execution view that defined Jinsight and is still there in TPTP allows me to more rapidly diagnose performance and funcional problems, literally in seconds sometimes.
Also TPTP is much more than a profiler, it's a broad and ambitious project,therefore suffers from a lack of polish.
There are some new demos on the TPTP docs page that are worth a look.
Paul (from my nokia 770 ;-)
Posted by: Paul Anderson | Dec 17, 2005 3:54:06 AM