Attaching JProfiler with your application was very simple no code, xmls, or any lengthy configuration was required. You can easily identify the resources leakages i.e. Streams, Memory, JDBC Resources, and other opened utilities. I got to know the benefit of using StringBuilder and StringBuffer after using JProfiler. It showed me in real life how changing or appending something in string can be so taxing on your resources. With it's help I was able to bring the heap space and memory used by my application from hundreds of MBs to just below 200 MBs. Review collected by and hosted on G2.com.

The paid version costs a lot. It could be cheaper. The software itself is slow, takes a lot of resources to run. If we are running our application and the profiler also on the same machine it makes the server response automatically slow as the resources employed by the Jprofiler usually exceeds than that of your application. Review collected by and hosted on G2.com.