DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5729>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5729 Tomcat standalone bogs down very badly under load [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-01-08 03:41 ------- Thanks for the report. I'm using ab for load testing, but I'm usually doing very focused testing to get the performance of the engine and solate hotspots (like, testing the connector only, testing static file serving, etc). I personally already know very well the hotspots in the standalone connector (which I'm rewriting at the moment) and other things like the static file serving. Kin-Man probably has similar insights on Jasper internals. The benchmark is way too generic to be of any use for development, as it is testing all the components put on top of each other. The problem with running out of processors is a bug (which I could never reproduce with 10s of ab runs with a concurrency of 50) which should be filed separately (after removing the comments in bold, of course). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
