JavaWorld Forums: JProfiler

I share the comment on "pure" online help for JProfiler. Especially I miss clear comments on the differences between the three CPU time collection modes. Using one or the other there are fundamental(!) differences in the results shown.
Although a "Clear results" button is really needed. Neverthelesss, I was able to monitor a complex server application within 15 minutes without needing looking much at the online help. It is a really intuitive tool. Monitoring a "remote" application that means launching an application is well supported by adding "start and stop" commands executed before the launch will happen. Without that feature I was not able to laucnh successfully because the application is a JVM started by executing the "start command." Starting "by hand" and trying to launch later on did not work. It did not work with JProbe too because the whole application was slowed down unacceptable.
Another interesting feature of JProfililer is a small API that allows to start and stop CPU profiling by the program under control. Again, the online help does not explain very well what really happens. There is much work do do in this field by the JProfiler people. But after all, I agree with the author: JProbe is too complex and has a poor GUI. Optimizeit is good but could not help me in my special environment. Thus JProfiler was my choice.

InfoWorld: Modernizing IT

JavaWorld: Solutions for Java Developers