well because this is for an 15K member organization, and that is a MAJOR change. I'm in charge of the web project, not the hardware, and as much as I've fought that battle, the best I've gotten was virtualization still on a 32-bit OS. I ordered 2 new 2K8 64b systems (still virtualized :: stroke ::) but they should take care of all the users. If I had my way it'd be different, but you know how corporate world is. Just like the military.... hurry up and wait. :)
I DID manage to get everything running mostly optimally. Here's what I did: in the environment variables I set JAVA_OPTS = -XX:MaxPermSize=256m -Xms=256M -Xmx=1536M. Now Tomcat runs FAST and with about 3000 users, it's still blazing along using about 150MB on each of the 4 boxes. Much better than 500MB per box, with 1500 users. If it needs more ram, I change the variables and bounce the TC Server. No biggie. Thanks again Charles! - Josh On Sun, Feb 5, 2012 at 11:37 PM, Caldarale, Charles R < chuck.caldar...@unisys.com> wrote: > > From: Josh Gooding [mailto:josh.good...@gmail.com] > > Subject: Re: unable to set MaxPermSize past 128MB > > > your kidding me right? Why is tweaking the JVM for this so hard? > > Why are you still running on ancient hardware and software? Use a 64-bit > OS and a 64-bit JVM and you don't have to be concerned with the inherent > limits of 32-bit environments. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received this in error, please contact the sender and delete the e-mail and > its attachments from all computers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
