I'm not totally clear on how you profiled the page. Did you use OptimizeIt/JProbe, or simply added a start time at the beginning and at the end. from first hand experience, I doubt the connector is the cause, but I could be wrong. What in your struts page is causing it to take 35 seconds? You might want to time the actual application process and see how much time it takes. In theory and practice reading the input into buffers scales better. What exactly does the page do with the input in the first place? peter
David Morris <[EMAIL PROTECTED]> wrote: I did some profiling of a slow page (Struts based) on a site using the Coyote connector. This site does not use Apache. It appeared that a java.net.SocketInputStream.read being invoked from org.apache.coyote.http11.InternalInputBuffer.parseRequestLine() was causing a bottleneck. In this case average response over a 5 page interaction with three being relatively simple and two being complex averaged 35 seconds per response when repeated 20 times. I changed the site to use the old and deprecated http connector and performance improved to 4 seconds per response. It appears that the org.apache.catalina.connector.http.SocketInputStream was much faster. Since Coyote is recommended, does anyone have any ideas on how I can get it to perform better? Over dozens of tests, it appears that large pages take a long time with the Coyote connector. Thanks, David Morris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software
