Slashdot Mirror

← Back to Stories (view on slashdot.org)

Build Your Own Java Performance Profiling Tool

Posted by ryuzaki0 on from the cuppa-diy-goodness dept.

An anonymous reader writes "IBM DeveloperWorks has an interesting look at creating a custom profiler using Java 5 and AOP. From the article: 'Profiling is a technique for measuring where software programs consume resources, including CPU time and memory. This article provides a list of best-of-breed features you might look for in an ideal profiler and explains why aspect-oriented techniques are well suited to achieving some of those features. It also introduces you to the JDK 5.0 agent interface and walks you through the steps of using it to build your own aspect-oriented profiler.'"

3 of 153 comments (clear)

  1. Re:If you're optimizing Java, you're sunk by HotBBQ · · Score: 5, Informative

    That's simply not true. I work on a large Java project that deals with a lot of matrix intensive work. Our Java code has been rigorously architected, engineered, and optimized. The matrix code in particular (where the majority of our processing time is spent) is far superior in Java than it was in C or C++. Every programming language has its place, use the one that suites your needs. Profiling most any code can reveal useful information.

  2. Re:Why? by animaal · · Score: 5, Funny

    I agree totally. Java is dead. We just have to get the message through to the huge numbers of organizations and developers who depend on the technology to get their jobs done. Oh, and then we have to come up with something better to replace it. Give me a little while... ;)

  3. Re:you really need more than hprof ? by andrewwilcox · · Score: 5, Informative
    As was noted in the article, hprof has a number of short falls:
    • It is slow. If you've spent any amount of time using hprof, then you know what I'm talking about!
    • You can't start and stop it at runtime. If you've ever tried to profile a web application with hprof, you know what I'm talking about!
    • Filtering. hprof profiles everything and so it's slow and that output is expansive. When I'm profiling code, I want to know how my code is performing, not how some third party library is performing.

    I like hprof -- it's helped me out more times that I can say, but it also has some short comings, which is why I developed JIP