jsalvata 2003/11/28 16:50:27 Modified: bin jmeter jmeter.bat Log: I had made a silly choice of a TargetSurvivorRatio. Not that it could make much harm, but just in case... Revision Changes Path 1.23 +1 -1 jakarta-jmeter/bin/jmeter Index: jmeter =================================================================== RCS file: /home/cvs/jakarta-jmeter/bin/jmeter,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- jmeter 27 Nov 2003 19:56:02 -0000 1.22 +++ jmeter 29 Nov 2003 00:50:26 -0000 1.23 @@ -28,7 +28,7 @@ # This ratio and target have been proven OK in tests with a specially high # amount of per-sample objects (the HtmlParserHTMLParser tests): -SURVIVOR="-XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=80%" +SURVIVOR="-XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=50%" # Think about it: trying to keep per-run objects in tenuring definitely # represents a cost, but where's the benefit? They won't disappear before 1.27 +1 -1 jakarta-jmeter/bin/jmeter.bat Index: jmeter.bat =================================================================== RCS file: /home/cvs/jakarta-jmeter/bin/jmeter.bat,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- jmeter.bat 28 Nov 2003 12:18:05 -0000 1.26 +++ jmeter.bat 29 Nov 2003 00:50:26 -0000 1.27 @@ -34,7 +34,7 @@ rem including some tuning recommendations set HEAP=-Xms256m -Xmx256m set NEW=-XX:NewSize=128m -XX:MaxNewSize=128m -set SURVIVOR=-XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=80% +set SURVIVOR=-XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=50% set TENURING=-XX:MaxTenuringThreshold=2 set EVACUATION=-XX:MaxLiveObjectEvacuationRatio=20% set RMIGC=-Dsun.rmi.dgc.client.gcInterval=600000 -Dsun.rmi.dgc.server.gcInterval=600000
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
