> > If your application > needs 64MB of > > Heap space and you allocate only -Xms16M, then right at the > start the > > JVM will have to increase the Heap to 64MB (minimum); so > why would you > > do that ? >
64MB was just a number I threw out. The app actually uses about 20MB at startup, so we might consider setting the minimum pool to 25M. > I can see the lure of "only taking what you need" and > allowing the JVM to automatically re-size the memory space: > that way, you only take up a huge chunk of memory during peak > load and not all the time. > > But why? > > If you are going to need, say, 512MiB at peak load, you're > going to need that memory available whether or not it is > allocated to the JVM itself at any given time. If that's the > case, why not let the JVM have that memory all the time? Because the server has about 100 instances of tomcat. They do not all need the memory at the same time. --Eric Disclaimer - February 17, 2012 This email and any files transmitted with it are confidential and intended solely for Tomcat Users List. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
