Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It is really difficult to find good article on Netbeans profiler. I found <a href="http://www.oracle.com/technetwork/java/index-156936.html" rel="nofollow noreferrer">this link</a> helpful. </p> <p>Summary of above three graphs is as below:</p> <p><strong>Graph (1)</strong> In 1st graph, red shading in the first graph indicates allocated size of the JVM heap while purple overlay indicates the amount of heap space actually in use. In this picture allocated heap size is around 450 MB out of which 140 MB is used to hold java objects.</p> <p><strong>Graph (2)</strong> 2nd graph shows heap statistics. </p> <ul> <li>Blue line is the % of execution time spent by the JVM doing GC. If you see blue line large percentage then you should increase JVM heap size.(-Xmx parameter). Proper analysis of GC frequency will allow you to determine if your app is facing problem or not. Keep in mind that GC related problems are unlikely to be caught during development or functional testing. Proper garbage collection tuning will require you to perform load and perform testing with high-volume from simultaneous users.</li> <li>Red line: Count of surviving generations is the % of different ages of the java objects on the JVM's heap. When the value of surviving generations is low it indicates that most of the objects on the heap have been around about the same amount of time. If however, the value for surviving generations is increasing at a highe rate over time then it indicates that your app is allocating new objects while maintaining references to many of the older objects it already allocated, so waste of memory or even memory leak.</li> </ul> <p><strong>Graph (3)</strong> 3rd Graph shows count of active threads in JVM. Too much variation of active counts of threads will eat CPU (context switching). </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload