-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter,
On 8/14/2009 7:52 AM, Peter Crowther wrote: > How many concurrent requests are you sending, and how are you sending > them? If you're testing your app using a single Web browser, most > browsers will not send more than two concurrent requests to the same > server. +1 Seeing that 2 CPUs are being used (instead of 8) probably means that the request (or requests) are being handled by a single thread each (which is exactly how it's supposed to work). If you are running a load test with many simultaneous requests, then either something is wrong with your test (and you are only actually doing 2 requests at a time) or something is wrong with your server configuration (and you only have 2 request processor threads configured). Seeing that the CPU load is "high" might not be a problem. I've seen DWM eat up 50% of my CPU just dragging a window around... I wouldn't trust Microsoft Windows' Task Manager CPU time metrics very much. If you find that you are pegging your CPU (that is, you actually can not add any more requests without significantly delaying the server responses) under very light load (such as 5-10 simultaneous requests) then you have no further to look than your own application. Tomcat is almost never the problem: no amount of configuration can stop your web application from sucking (unless you have implemented your own "suck" setting, in which case you should always set it to "false" in production). > 3) Take a thread dump. http://wiki.apache.org/tomcat/HowTo#head-a3243c1d640297a9f2aa9446cbed434efbd4d1d9 - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqFd1AACgkQ9CaO5/Lv0PDV2gCcDGh9oljj/AO2Ukqkcq17BuU0 P18AnRQfGfKQltJP1jGWRAW26tebe1zN =7Z3h -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
