sebb        2005/05/28 04:07:41

  Modified:    xdocs/usermanual component_reference.xml
  Added:       xdocs/images/screenshots/timers
                        constant_throughput_timer.png
  Removed:     xdocs/images/screenshots/timers
                        constant_throughput_timer.gif
  Log:
  Document Throughput Timer legacy mode
  
  Revision  Changes    Path
  1.1                  
jakarta-jmeter/xdocs/images/screenshots/timers/constant_throughput_timer.png
  
        <<Binary file>>
  
  
  1.113     +8 -3      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.112
  retrieving revision 1.113
  diff -u -r1.112 -r1.113
  --- component_reference.xml   28 May 2005 10:17:31 -0000      1.112
  +++ component_reference.xml   28 May 2005 11:07:41 -0000      1.113
  @@ -1594,7 +1594,7 @@
   If you want to match /images at the start of a string only, use the value 
"^/images".
   Jakarta ORO also supports zero-width look-ahead, so one can match 
/images/... 
   but retain the trailing / in the output by using "^/images(?=/)".
  -Note that the current version of Jakara ORO does not support look-behind - 
i.e. "(?<=...)".
  +Note that the current version of Jakara ORO does not support look-behind - 
i.e. "(?&lt;=...)".
   <br></br>
   If there are any problems interpreting any variables as patterns, these are 
reported in jmeter.log,
   so be sure to check this if UDVs are not working as expected.
  @@ -2060,7 +2060,7 @@
   
   </component>
   
  -<component index="16.6.4" name="Constant Throughput Timer" 
screenshot="timers/constant_throughput_timer.gif">
  +<component index="16.6.4" name="Constant Throughput Timer" 
screenshot="timers/constant_throughput_timer.png">
   
   <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>
   
  @@ -2069,6 +2069,11 @@
   <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>
  +  <property name="Legacy Mode" required="Yes">
  +     If True, calculate throughput for each thread separately.
  +     <br></br>
  +     If False, calculate throughput based on the total number of threads.
  +     </property>
   </properties>
   
   </component>
  
  
  

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

Reply via email to