You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jmeter.apache.org by pm...@apache.org on 2016/01/03 23:31:41 UTC

svn commit: r1722764 - /jmeter/trunk/xdocs/usermanual/best-practices.xml

Author: pmouawad
Date: Sun Jan  3 22:31:40 2016
New Revision: 1722764

URL: http://svn.apache.org/viewvc?rev=1722764&view=rev
Log:
Clarify documentations by removing old versions mention

Modified:
    jmeter/trunk/xdocs/usermanual/best-practices.xml

Modified: jmeter/trunk/xdocs/usermanual/best-practices.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/best-practices.xml?rev=1722764&r1=1722763&r2=1722764&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/best-practices.xml (original)
+++ jmeter/trunk/xdocs/usermanual/best-practices.xml Sun Jan  3 22:31:40 2016
@@ -52,8 +52,7 @@ For testing how JMeter performs on a giv
 It does not require any network access so can give some idea as to the maximum throughput achievable.
 </p>
 <p>
-JMeter versions since 2.8 have an option to delay thread creation until the thread
-starts sampling, i.e. after any thread group delay and the ramp-up time for the thread itself.
+JMeter has an option to delay thread creation until the thread starts sampling, i.e. after any thread group delay and the ramp-up time for the thread itself.
 This allows for a very large total number of threads, provided that not too many are active concurrently.
 </p>
 </section>