svn commit: r383368 - in /jakarta/jmeter/branches/rel-2-1/xdocs/usermanual: build-test-plan.xml test_plan.xml

[se...@apache.org]

Author: sebb
Date: Sun Mar  5 11:01:16 2006
New Revision: 383368

URL: http://svn.apache.org/viewcvs?rev=383368&view=rev
Log:
Tidy up documentation

Modified:
    jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/build-test-plan.xml
    jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/test_plan.xml

Modified: jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/build-test-plan.xml
URL: http://svn.apache.org/viewcvs/jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/build-test-plan.xml?rev=383368&r1=383367&r2=383368&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/build-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/build-test-plan.xml Sun Mar  5 11:01:16 2006
@@ -47,7 +47,6 @@
 JMeter will save the element selected, plus all child elements beneath it.  In this way,
 you can save test tree fragments, individual elements, or the entire test plan.</p>
 
-<note>The test plan file format changed with version 1.7. Versions later than 1.8 are no longer capable of reading test plans in the old format. If you need to use an old test plan, use JMeter 1.7 or 1.8 to load and re-save it in the new format.</note>
 </subsection>
 
 <subsection name="3.3 Configuring Tree Elements" anchor="config_element">

Modified: jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/test_plan.xml
URL: http://svn.apache.org/viewcvs/jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/test_plan.xml?rev=383368&r1=383367&r2=383368&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/test_plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-1/xdocs/usermanual/test_plan.xml Sun Mar  5 11:01:16 2006
@@ -54,16 +54,24 @@
 start 10 (100/10) seconds after the previous thread was begun.  If there are 30 threads
 and a ramp-up period of 120 seconds, then each successive thread will be delayed by 4 seconds.</p>
 
-<p>By default, a thread group is configured to loop indefinitely through its elements.
-Alternatively, you can set the number of times the thread group will loop before ending.  If the number
-is set at one, then JMeter will execute the test only once before stopping.</p>
+<p>Ramp-up needs to be long enough to avoid too large a work-load at the start
+of a test, and short enough that the last threads start running before
+the first ones finish (unless one wants that to happen).
+</p>
+<p>
+Start with Ramp-up = number of threads and adjust as needed.
+</p>
+
+<p>By default, the thread group is configured to loop once through its elements.</p>
 
 <p>Version 1.9 introduces a test run <b>scheduler</b>. 
-	Click the checkbox at the bottom of the Thread Group panel to reveal two extra fields
+	Click the checkbox at the bottom of the Thread Group panel to reveal extra fields
 	 in which you can enter the start and end times of the run. 
 	 When the test is started, JMeter will wait if necessary until the start-time has been reached.
 	 At the end of each cycle, JMeter checks if the end-time has been reached, and if so, the run is stopped,
 	 otherwise the test is allowed to continue until the iteration limit is reached.</p>
+	 <p>Alternatively, one can use the relative delay and duration fields. 
+	 Note that delay overrides start-time, and duration over-rides end-time.</p>
 </subsection>
 
 <subsection name="4.2 Controllers" anchor="controllers">



---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org