Hi again
thanks for the link, a useful resource.

Surprisingly I found the same latency description in the glossary:
http://jakarta.apache.org/jmeter/usermanual/glossary.html

So, I've known enough about the latency and the load time (http://www.mail-archive.com/[email protected]/msg19328.html)

Deepak Shetty wrote:
Hi
From Sebb
"JMeter measures the latency from just before sending the request to just
after the first response has been received. Thus the time
includes all the processing needed to assemble the request as well as
assembling the response, which in general will be longer than one byte."

http://www.mail-archive.com/[email protected]/msg18437.html

regards
deepak


On Thu, Oct 15, 2009 at 1:09 PM, Nikolay_Miroshnichenko
<[email protected]>wrote:

I guess it's not a new question but I couldn't find an exact answer and I'm
still confused in realizing the differences between the Load Time and the
Latency.

My guesses: the latency is a waiting time from the point of sending a
request to the point of receiving the first byte of the response.
And the load time is latency plus time of downloading the whole body of the
response. Is that both correct?

As I've noticed, they either slightly differ (latency is shorter) or equal
(almost always).

Here is an example:

Thread Name: NewUsers 1-782
Sample Start: 2009-10-10 23:11:29 MSD
Load time: 47762
Latency: 47734
Size in bytes: 589641
Sample Count: 1
Error Count: 0
Response code: 200
Response message: OK

and another:

Thread Name: NewUsers 1-939
Sample Start: 2009-10-10 23:12:16 MSD
Load time: 479
Latency: 452
Size in bytes: 589641
Sample Count: 1
Error Count: 0
Response code: 200
Response message: OK

--
Best Regards
Nikolay Miroshnichenko




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]




--
Best Regards
Nikolay Miroshnichenko


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to