-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
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%)
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..
Thanks for the suggestion. The clients connect by IP address
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric,
On 7/3/2009 10:42 PM, Robinson, Eric wrote:
I just want to be sure of one thing. Does the value represent the total
time from the moment tomcat saw the client's request to the time it
successfully delivered the full response?
You can always
That's very helpful, Chris.
The bytes are not guaranteed to have arrived at the client by the time
the valve computes the elapsed time.
Right, but is it generally correct to say that the response time value
represents the time from when the request was received to the time the
response was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric,
On 7/5/2009 10:07 AM, Robinson, Eric wrote:
That's very helpful, Chris.
The bytes are not guaranteed to have arrived at the client by the time
the valve computes the elapsed time.
Right, but is it generally correct to say that the
Chris,
Your question makes me think that perhaps what you're
seeing is a timing-out keep-alive request:
It's not what I'm seeing in the logs, it's what the customer is seeing
in the application. One of my customers says they are frequently seeing
long application delays on all of the
