You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by wo...@apache.org on 2005/09/06 20:24:30 UTC
cvs commit: jakarta-jmeter/xdocs/usermanual build-monitor-test-plan.xml
woolfel 2005/09/06 11:24:30
Modified: xdocs/usermanual Tag: rel-2-1 build-monitor-test-plan.xml
Log:
fixing a typo. this fixes bug 36516
peter
Revision Changes Path
No revision
No revision
1.8.2.1 +3 -3 jakarta-jmeter/xdocs/usermanual/build-monitor-test-plan.xml
Index: build-monitor-test-plan.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/build-monitor-test-plan.xml,v
retrieving revision 1.8
retrieving revision 1.8.2.1
diff -u -r1.8 -r1.8.2.1
--- build-monitor-test-plan.xml 18 Jun 2005 18:04:45 -0000 1.8
+++ build-monitor-test-plan.xml 6 Sep 2005 18:24:29 -0000 1.8.2.1
@@ -146,7 +146,7 @@
the right is dead/healthy. If the memory line spikes up and down rapidly, it could
indicate memory thrashing. In those situations, it is a good idea to profile the
application with Borland OptimizeIt or JProbe. What you want to see is a regular
-pattern for load, memory and threads. Any irratic behavior usually indicates poor
+pattern for load, memory and threads. Any erratic behavior usually indicates poor
performance or a bug of some sort.</p>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org