woolfel 2004/06/18 05:53:23 Modified: xdocs/usermanual component_reference.xml Log: added documentation about the Distribution graph.
peter Revision Changes Path 1.92 +20 -1 jakarta-jmeter/xdocs/usermanual/component_reference.xml Index: component_reference.xml =================================================================== RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/component_reference.xml,v retrieving revision 1.91 retrieving revision 1.92 diff -u -r1.91 -r1.92 --- component_reference.xml 12 Jun 2004 17:11:45 -0000 1.91 +++ component_reference.xml 18 Jun 2004 12:53:23 -0000 1.92 @@ -1009,6 +1009,25 @@ </description> </component> +<component index="15.3.11" name="Distribution Graph" screenshot="distribution_graph.png"> +<description> +<p>The distribution graph will display a bar for every unique response time. Since the +granularity of System.currentTimeMillis() is 10 milliseconds, the 90% threshold should be +within the width of the graph. The graph will draw two threshold lines: 50% and 90%. +What this means is 50% of the response times finished between 0 and the line. The same +is true of 90% line. Several tests with Tomcat were performed using 30 threads for 600K +requests. The graph was able to display the distribution without any problems and both +the 50% and 90% line were within the width of the graph. A performant application will +generally produce results that clump together. A poorly written application that has +memory leaks may result in wild fluctuations. In those situations, the threshold lines +may be beyond the width of the graph. The recommended solution to this specific problem +is fix the webapp so it performs well. If your test plan produces distribution graphs +with no apparent clumping or pattern, it may indicate a memory leak. The only way to +know for sure is to use a profiling tool.</p> +</description> +</component> + + </section> <section name="15.4 Configuration Elements" anchor="config_elements"> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
