-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bruce,
On 11/18/2009 9:48 AM, Bruce Foster wrote: > I'm new to the list and tomcat. Welcome! > I have a web application deployed in tomcat 6. this application is > quite CPU hungry and I would like to optimise the tomcat accordingly. > > I'm expecting to have 200 concurrent connections to the server at > peak, not much for a standard web application but ours is imagery > based and bit resource hungry. Can you be more specific about what resources your webapp is hungry for? If a typical request needs 10MiB of memory to process an image, then you'll need to make sure that 50MiB * 200 requests = 10GiB of heap space is available to your webapp. Can your webapp handle 200 simultaneous requests? Consider using a load-testing tool such as JMeter to see how your webapp performs under load. Watch heap usage (in the JVM! 'Task Manager' is not useful, here), CPU utilization, disk usage, etc. to see what appears to be your limiting resource(s) and then tackle those. You already know the number of concurrent requests you are expecting at peak (200), so you have sort of set that requirement already (though I might allocate 225 or 250 just in case you get some bursts in there). Memory (and GC behavior) is really the only thing you can tune at the JVM level. Generally speaking, more heap space is better if you're going to need it. Also, setting the min and max heap sizes to the same values will avoid heap re-sizing which just wastes time if you know you want that memory dedicated to the heap anyway. Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksEUPEACgkQ9CaO5/Lv0PBqMwCfaTsem7ypj+aPTloqlDDKGI69 zXQAn1UjW0kB5q3RvppuLCjRwT9CJ6YT =t0x1 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
