svn commit: r1723538 - in /jmeter/trunk: bin/jmeter bin/jmeter.bat xdocs/changes.xml

[se...@apache.org]

Author: sebb
Date: Thu Jan  7 13:31:08 2016
New Revision: 1723538

URL: http://svn.apache.org/viewvc?rev=1723538&view=rev
Log:
JVM don't recognize option MaxLiveObjectEvacuationRatio; remove from comments
Bugzilla Id: 58814

Modified:
    jmeter/trunk/bin/jmeter
    jmeter/trunk/bin/jmeter.bat
    jmeter/trunk/xdocs/changes.xml

Modified: jmeter/trunk/bin/jmeter
URL: http://svn.apache.org/viewvc/jmeter/trunk/bin/jmeter?rev=1723538&r1=1723537&r2=1723538&view=diff
==============================================================================
--- jmeter/trunk/bin/jmeter (original)
+++ jmeter/trunk/bin/jmeter Thu Jan  7 13:31:08 2016
@@ -71,6 +71,8 @@ PRGDIR=`dirname "$PRG"`
 # on Sun JVMs. Following is the analysis on which it is based. If it's total
 # gibberish to you, please study my article at
 # http://www.atg.com/portal/myatg/developer?paf_dm=full&paf_gear_id=1100010&detailArticle=true&id=9606
+# Original page has disappeared, it is now only available at: 
+# https://web.archive.org/web/20060614151434/http://www.atg.com/portal/myatg/developer?paf_dm=full&paf_gear_id=1100010&detailArticle=true&id=9606
 #
 # JMeter objects can generally be grouped into three life-length groups:
 #
@@ -108,13 +110,6 @@ HEAP="-Xms512m -Xmx512m"
 #
 TENURING="-XX:MaxTenuringThreshold=2"
 
-# This evacuation ratio is OK (see the comments for SURVIVOR) during test
-# runs -- not so sure about operations that bring a lot of long-lived information into
-# memory in a short period of time, such as loading tests or listener data files.
-# Increase it if you experience OutOfMemory problems during those operations
-# without having gone through a lot of Full GC-ing just before the OOM:
-# EVACUATION="-XX:MaxLiveObjectEvacuationRatio=20%"
-
 # Java 8 remove Permanent generation, don't settings the PermSize
 if [ $current_version -lt "8" ]; then
     # Increase MaxPermSize if you use a lot of Javascript in your Test Plan :
@@ -131,6 +126,6 @@ DUMP="-XX:+HeapDumpOnOutOfMemoryError"
 
 SERVER="-server"
 
-ARGS="$SERVER $DUMP $HEAP $NEW $SURVIVOR $TENURING $EVACUATION $PERM $CLASS_UNLOAD"
+ARGS="$SERVER $DUMP $HEAP $NEW $SURVIVOR $TENURING $PERM $CLASS_UNLOAD"
 
 java $ARGS $JVM_ARGS $JMETER_OPTS -jar "$PRGDIR/ApacheJMeter.jar" "$@"

Modified: jmeter/trunk/bin/jmeter.bat
URL: http://svn.apache.org/viewvc/jmeter/trunk/bin/jmeter.bat?rev=1723538&r1=1723537&r2=1723538&view=diff
==============================================================================
--- jmeter/trunk/bin/jmeter.bat (original)
+++ jmeter/trunk/bin/jmeter.bat Thu Jan  7 13:31:08 2016
@@ -73,7 +73,8 @@ set JMETER_CMD_LINE_ARGS=%*
 rem The following link describes the -XX options:
 rem http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html
 rem http://java.sun.com/developer/TechTips/2000/tt1222.html has some more descriptions
-rem Unfortunately TechTips no longer seem to be available
+rem Unfortunately TechTips no longer seem to be available, except via:
+rem https://web.archive.org/web/20090614101951/http://java.sun.com/developer/TechTips/2000/tt1222.html
 
 rem See the unix startup file for the rationale of the following parameters,
 rem including some tuning recommendations

Modified: jmeter/trunk/xdocs/changes.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/changes.xml?rev=1723538&r1=1723537&r2=1723538&view=diff
==============================================================================
--- jmeter/trunk/xdocs/changes.xml (original)
+++ jmeter/trunk/xdocs/changes.xml Thu Jan  7 13:31:08 2016
@@ -167,6 +167,7 @@ Summary
 <li><bug>58165</bug>Show the time elapsed since the start of the load test in GUI mode. Partly based on a contribution from Maxime Chassagneux (maxime.chassagneux at gmail.com)</li>
 <li><bug>58784</bug>Make JMeterUtils#runSafe sync/async awt invocation configurable and change the visualizers to use the async version.</li>
 <li><bug>58790</bug>Issue in CheckDirty and its relation to ActionRouter</li>
+<li><bug>58814</bug>JVM don't recognize option MaxLiveObjectEvacuationRatio; remove from comments</li>
 </ul>
 <ch_section>Non-functional changes</ch_section>
 <ul>