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 2015/03/07 12:19:55 UTC

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

Author: pmouawad
Date: Sat Mar  7 11:19:54 2015
New Revision: 1664819

URL: http://svn.apache.org/r1664819
Log:
Typo
Update some infos
Try to encourage version migration.

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=1664819&r1=1664818&r2=1664819&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/best-practices.xml (original)
+++ jmeter/trunk/xdocs/usermanual/best-practices.xml Sat Mar  7 11:19:54 2015
@@ -34,7 +34,8 @@
 
 <section name="&sect-num;.1 Always use latest version of JMeter" anchor="use_latest_version">
 <p>The performance of JMeter is being constantly improved, so users are highly encouraged to use the most up to date version. <br/>
-Ensure you always read <a href="../changes.html">changes list</a> to be aware of new improvements and components:
+Ensure you always read <a href="../changes.html">changes list</a> to be aware of new improvements and components.
+You should absolutely avoid using versions that are older than 3 versions before the last one.
 </p>
 </section>
 
@@ -105,7 +106,7 @@ with "${server}".
 
 </p>
 <p>
-If JMeter does not record any samples, check that the brower really is using the proxy.
+If JMeter does not record any samples, check that the browser really is using the proxy.
 If the browser works OK even if JMeter is not running, then the browser cannot be using the proxy.
 Some browsers ignore proxy settings for localhost or 127.0.0.1; try using the local hostname or IP instead.
 </p>
@@ -365,7 +366,7 @@ The appropriate property file can be pas
 <section name="&sect-num;.12 JSR223 Elements" anchor="jsr223">
 <p>
 For intensive load testing, the recommended scripting language is one whose ScriptingEngine implements the Compilable interface.
-Groovy scripting engine implements Compilable. However neither Beanshell nor Javascript do so as of release date of JMeter 2.10, so it is 
+Groovy scripting engine implements Compilable. However neither Beanshell nor Javascript do so as of release date of JMeter 2.13, so it is 
 recommended to avoid them for intensive load testing. 
 [Note: Beanshell implements the Compilable interface but it has not been coded - the method just throws an Exception.
 JMeter has an explicit work-round for this bug.]