jsalvata    2002/12/27 17:50:35

  Modified:    xdocs/usermanual component_reference.xml test_plan.xml
  Log:
  Documented Constant Throughput Timer.
  
  Revision  Changes    Path
  1.28      +13 -0     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.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- component_reference.xml   15 Oct 2002 20:28:42 -0000      1.27
  +++ component_reference.xml   28 Dec 2002 01:50:35 -0000      1.28
  @@ -803,6 +803,19 @@
   </properties>
   
   </component>
  +
  +<component index="13.6.4" name="Constant Throughput Timer" 
screenshot="../images/screenshots/timers/constant_throughput_timer.gif">
  +
  +<description><p>This timer introduces variable pauses, calculated to keep the total 
throughput (in terms of samples per minute) as close as possible to a give figure. Of 
course the throughput will be lower if the server is not capable of handling it, or if 
other timers or time-consuming test elements prevent it.</p>
  +
  +<p>Only samples within the container where you put the timer count towards the 
calculated throughput. Also note that the total time (used in the denominator to 
calculate the throughput) starts counting with the first such sample -- not with the 
test start.</p></description>
  +
  +<properties>
  +     <property name="Name" required="No">Descriptive name for this timer that is 
shown in the tree. </property>
  +  <property name="Target Throughput" required="Yes">Throughput we want the timer to 
try to generate.</property>
  +</properties>
  +
  +</component>
   </section>
   
   <section name="13.7 Modifiers" anchor="Modifiers">
  
  
  
  1.7       +2 -3      jakarta-jmeter/xdocs/usermanual/test_plan.xml
  
  Index: test_plan.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/test_plan.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- test_plan.xml     29 Jun 2002 00:37:00 -0000      1.6
  +++ test_plan.xml     28 Dec 2002 01:50:35 -0000      1.7
  @@ -191,13 +191,12 @@
   <subsection name="4.4 Timers" anchor="timers">
   
   <p>By default, a JMeter thread sends requests without pausing between each request.
  -We recommend that you specify a delay by adding one of the three timers to
  +We recommend that you specify a delay by adding one of the available timers to
   your Thread Group. If you do not add a delay, JMeter could overwhelm your server by
   making too many requests in a very short amount of time.</p>
   
   <p>The timer will cause JMeter to delay a certain amount of time between each
  -request that a thread makes.  Remember, threads are independent of one
  -another, and this applies to the timer delay as well.</p>
  +request that a thread makes.</p>
   
   <p>
   If you choose to add more than one timer to a Thread Group, JMeter takes the sum of
  
  
  

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to