-Xms is the minimum heap size -Xmx is the max heap size -XX:NewSize - if I remember correctly, it sets the size of new heap allocation. when this is set bigger, the vm has to allocate new heap memory less.
the last one I could be wrong. peter On Tue, 24 Aug 2004 06:51:49 -0600, Michael Chandler <[EMAIL PROTECTED]> wrote: > Maybe this is a dumb question but is there a way I can tell what the > heap size is before I try setting it? Or what is available? Can you tell > me the relationship between -Xms/-Xmx and -XX:NewSize/-XX:MaxNewSize? > Maybe this will help me understand the two settings. > > > > -----Original Message----- > From: Peter Lin [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 24, 2004 6:38 AM > To: JMeter Users List > Subject: Re: win 2000 > > that's strange. when I run it with and without the extra options on my > gateway laptop running XP and my old P3 450 it is faster if I just > have "-server" without all the extra options. > > maybe it's just my system or configuration. > > peter > > On Tue, 24 Aug 2004 13:13:29 +0200, Jordi Salvat i Alabart > <[EMAIL PROTECTED]> wrote: > > It's exactly the opposite: you'll want those parameters (tuned as > > suggested in the script's comments) when you need to generate high > loads > > -- that is: in actual use, not during development. > > > > These settings minimise (or almost) the amount of time spent in > garbage > > collection. This increases maximum throughput (i.e. the amount of > > traffic you can generate with a given machine and a given script). > They > > also reduce the frequency of full GCs to a minimum (most tests running > > for only a few hours will never need a full GC) thus reducing > > measurement error. > > > > I can't tell why Michael is getting that error with the HEAP options > in > > place -- those default parameters work well for me with JDK 1.4.2_03 > (I > > don't have _04 at hand). > > > > But removing the -Xms/-Xmx without removing the > > -XX:NewSize/-XX:MaxNewSize as he did in his last message causes > exactly > > that (as I would expect: the default heap is far too small to > accomodate > > a 128m new space). So leave all those parameters in place or remove > them > > all. > > > > -- > > Salut, > > > > Jordi. > > > > En/na Peter Lin ha escrit: > > > > > > > can you try commenting out all the extra VM parameters? > > > > > > usually I do that, since many of the settings really shouldn't be > used > > > for regular use. It's good for developers writing samplers and > > > plugins, but not necessarily great for just running tests. > > > > > > peter > > > > > > > > > On Mon, 23 Aug 2004 13:16:16 -0600, Michael Chandler > > > <[EMAIL PROTECTED]> wrote: > > > > > >>I installed j2sdk1.4.2_04. The same on both XP and win2k. I also > have > > >>j2sdk1.4.0-rc and j2sdk1.4.0_01. The newer one is first in my path > and > > >>classpath. > > >> > > >>Here is the echo (without [HEAP=-Xms256m -Xmx256m]): > > >>echo %JAVA_HOME%\bin\java %JVM_ARGS% %ARGS% -jar ApacheJMeter.jar > > >>%JMETER_CMD_LINE_ARGS% > > >> > > >>c:\j2sdk1.4.2_04\bin\java -XX:NewSize=128m -XX:MaxNewSize=128m > > >>-XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=50 > > >>-XX:MaxTenuringThreshold=2 -XX:MaxLiveObjectEvacuationRatio=20 > > >>-Dsun.rmi.dgc.client.gcInterval=600000 > > >>-Dsun.rmi.dgc.server.gcInterval=600000 -XX:PermSize=64m > > >>-XX:MaxPermSize=64m -verbose:gc -XX:+PrintTenuringDistribution -jar > > >>ApacheJMeter.jar > > >>Error occurred during initialization of VM > > >>Incompatible initial and maximum heap sizes specified > > >> > > >>-----Original Message----- > > >>From: BAZLEY, Sebastian [mailto:[EMAIL PROTECTED] > > >>Sent: Monday, August 23, 2004 12:16 PM > > >>To: 'JMeter Users List' > > >>Subject: RE: win 2000 > > >> > > >>Did you install the full JDK, or just the JRE? > > >> > > >>Some of the options may only make sense if the "server" flavour of > the > > >>JVM > > >>is installed. > > >> > > >>Certainly java -server only works if the full JDK is installed ... > > >> > > >>S. > > >>-----Original Message----- > > >>From: Michael Chandler [mailto:[EMAIL PROTECTED] > > >>Sent: 23 August 2004 19:07 > > >>To: JMeter Users List > > >>Subject: RE: win 2000 > > >> > > >>If I take it out, it still gives me the error. I'll try rebooting > here > > >>in a minute and do it again. I've tried several combos. I'll look at > > >>java - X, also. > > >> > > >>-----Original Message----- > > >>From: Peter Lin [mailto:[EMAIL PROTECTED] > > >>Sent: Monday, August 23, 2004 11:55 AM > > >>To: JMeter Users List > > >>Subject: Re: win 2000 > > >> > > >>it should work if you remove it. I have JMeter 2 and 1.9 running on > my > > >>workstation at home, which is running win2K. it works with Sun > > >>jdk1.4.2_03 and jdk5 > > >> > > >>peter > > >> > > >>On Mon, 23 Aug 2004 11:44:58 -0600, Michael Chandler > > >><[EMAIL PROTECTED]> wrote: > > >> > > >>>I've been running Jmeter successfully on my XP box. When I try to > run > > >> > > >>it > > >> > > >>>on a Win 2000 box, I get the error: > > >>> > > >>>Error occurred during initialization of VM > > >>>Incompatible initial and maximum heap sizes specified. > > >>> > > >>>The jmeter.bat file has the entry: > > >>>set HEAP=-Xms256m -Xmx256m > > >>> > > >>>I tried resetting it but haven't found the correct combination. > > >>> > > >>>Any ideas? > > >>> > > >>> > > >> > > > >>--------------------------------------------------------------------- > > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > > >>For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > > >>--------------------------------------------------------------------- > > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > > >>For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > >> > > >>_______________________________________________________ > > >> > > >>This e-mail and the documents attached are confidential and intended > > >>solely for the addressee; it may also be privileged. If you receive > this > > >>e-mail in error, please notify the sender immediately and destroy > it. > > >>As its integrity cannot be secured on the Internet, the Atos Origin > > >>group > > >>liability cannot be triggered for the message content. Although the > > >>sender endeavours to maintain a computer virus-free network, the > > >>sender does not warrant that this transmission is virus-free and > will > > >>not be liable for any damages resulting from any virus transmitted. > > >>_______________________________________________________ > > >> > > >> > > >> > > >> > > > >>--------------------------------------------------------------------- > > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > > >>For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > > >>--------------------------------------------------------------------- > > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > > >>For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > >> > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
