Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eric,
On 7/5/2009 2:56 PM, Robinson, Eric wrote:
TOTAL REQUESTS: 43865
AVERAGE RESPONSE TIME: 18 ms
RESPONSE TIME BREAKDOWN:
0 - 10 ms: 36454 (83.00%)
11 - 50 ms: 6128 (13.00%)
51 - 100 ms: 436 (0%)
101 - 250 ms: 453 (1.00%)
251 - 500 ms: 230 (0%)
501 - 1000 ms: 62 (0%)
1001 - 2500 ms: 41 (0%)
2501 - 5000 ms: 7 (0%)
5001 - 10000 ms: 54 (0%)
10001 - 20000 ms: 0 (0%)
20000+ ms : 0 (0%)
To me, this looks like healthy response time.
I agree. I would run a remote benchmark to confirm that it's the
/customer's/ network that has problems; I suspect that's where you'll
find the problem.
I would add that one good place to /start/ looking, is the DNS name
resolution of your customer's workstations.
Because if that is not working properly, then your server won't even see
the request for a while after they click..
A simple "nslookup your.server.name" from a customer workstation will
already tell you some.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
