Aryeh Katz wrote:
>Did you try getting the max throughtput using another servlet ? If
>there's a performance problem with your servlet, you could use
>something like OptimizeIt to figure it improve it.
I downloaded OptimizeIt, ran it on my servlet and ran ab.
As expected most of the CPU time was in the AJP stuff, and most of the
AJP stuff was in my servlet.
However, the majority of the processing being done was PrintWriter.flush.
Contrary to some of the other posts here, I didn't see anything in
StringBuffer.replace.
I'm basing this on the CPU profiler. If there is something else I should look at,
please let me know
I can't see why PrintWriter.flush() (probably called in CoyoteWriter.flush()) takes so much CPU time. If it is confirmed to be a problem, then we can reimplement the functions instead of relying on the superclass.
What you may want to experiment with:
- use JDK 1.4.1 (faster)
- try Tomcat standalone (JK has more overhead than standalone Tomcat)
Otherwise, can you send more details of the profile ? I didn't see a spike in that function while profiling JSPs or the HelloWorld servlet, which both use the CoyoteWriter.
Thanks,
R�my
--
To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
