On 2/12/2011 1:27 PM, Tony Anecito wrote:
Right now for most of my transactions I get less than 5 microseconds and around
1.2msec is spent on getting to and out of Tomcat and out of to/out of the client
call.
So people were saying look at better parsers or replacing whatever does the
parsing.
I am measuring round trip time at the client (before and after the jersey call)
and getting to 1.47msec. At Tomcat it is less than 5microseconds at the
beginning of the method the GET goes to the end of the method so the code is
very fast.
So I am thinking whatever parses the cmd and puts together the html response
after the end of the method is where I should focus.
The network goes over a 1Gb ethernet lan.
When you're looking at low- or sub-millisecond timing, you're going to
need to look at your network router (if any), switch and wiring latency,
as well as the raw throughput..
D
Regards,
-Tony
----- Original Message ----
From: Mark Thomas<ma...@apache.org>
To: Tomcat Users List<users@tomcat.apache.org>
Sent: Sat, February 12, 2011 11:18:18 AM
Subject: Re: Performance Tuning Tomcat 7...
On 12/02/2011 18:14, Tony Anecito wrote:
Is there any performance tuning that can be done to Tomcat 7 besides just the
standard jvm arguments?
95%+ of tuning will need to be done in the app rather than Tomcat. My
recommendation is to get yourself a profiler and go from there.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
