You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@jmeter.apache.org by se...@apache.org on 2017/02/20 12:37:02 UTC

svn commit: r1783750 - /jmeter/trunk/bin/testfiles/BatchTestLocal.jmx

Author: sebb
Date: Mon Feb 20 12:37:02 2017
New Revision: 1783750

URL: http://svn.apache.org/viewvc?rev=1783750&view=rev
Log:
Increase rampup to try and ensure first thread has time to complete even on a busy system

Modified:
    jmeter/trunk/bin/testfiles/BatchTestLocal.jmx

Modified: jmeter/trunk/bin/testfiles/BatchTestLocal.jmx
URL: http://svn.apache.org/viewvc/jmeter/trunk/bin/testfiles/BatchTestLocal.jmx?rev=1783750&r1=1783749&r2=1783750&view=diff
==============================================================================
--- jmeter/trunk/bin/testfiles/BatchTestLocal.jmx (original)
+++ jmeter/trunk/bin/testfiles/BatchTestLocal.jmx Mon Feb 20 12:37:02 2017
@@ -24,7 +24,7 @@
         </elementProp>
         <longProp name="ThreadGroup.end_time">1172922900000</longProp>
         <stringProp name="ThreadGroup.on_sample_error">continue</stringProp>
-        <stringProp name="ThreadGroup.ramp_time">20</stringProp>
+        <stringProp name="ThreadGroup.ramp_time">80</stringProp>
         <stringProp name="TestPlan.comments">N.B. The ramp-up period is set so that the first thread will finish before the second.
 This is to ensure the test output is predictable, whilst still allowing testing of unshared counter etc</stringProp>
       </ThreadGroup>