Since I wrote the sampler and documentation, I'll try to explain it the best I can.
the performance graph has 4 lines. health - this line is sort of arbitrary at the moment, but it basically takes the load and threads to calculate health load - combination of memory and threads memory - free memory/total used threads - busy/total threads The expected behavior of the graph is the memory usage will show a regular pattern. The red thread line should remain constant under constant load. if the red line increases rapidly, it means there's threading issues in the webapp. the load should show a regular pattern under constant load, since it is a combination of memory and thread stats. hope that helps peter On 2/28/06, Noureddine BEKRAR <[EMAIL PROTECTED]> wrote: > > Hi, > > Can you please tell me which memory is monitored in the "performance > graph" of the "monitor results listener", is it the size of the used memory > for the JVM or is it the memory used by Tomcat. > This is the -not enough clear- explanation about this subject in the > "Building Monitor testplan" > > http://jakarta.apache.org/jmeter/usermanual/build-monitor-test-plan.html : > > > ... The performance graph shows for different lines. The free memory line > shows how much free memory is left in the current allocated block. Tomcat 5 > returns the maximum memory, but it is not graphed. In a well tuned > environment, the server should never reach the maximum memory... > >
