Re: Incorrect timings in Grinder..!!

Hi Gary,
Thanks for the quick response. From the chrome browser, i noted the first
time i made the request and i made other requests using Ctrl+F5 which makes
sure i get a 200 OK response and not from the cache. I made about 10 calls
and i always got a time of 1.2-1.5 seconds (including the first).

>From grinder, i noted noted the times for each request and i always found
that it took > 2.3 seconds. Its a simple HTTP request from grinder. *
request.POST (url, headers, body) *.

Can you give a theory as to how the browser managers to get it in 1.2
seconds and the same in Grinder takes 2.5 seconds..? Do you think there are
any optimizations being done by the browser?

--PS: I will have to test JAVA code again, coz, i didn't bother about it
much after seeing the difference between browser and grinder timings. I
might have just gotten lucky.



-----
Kirti
--
View this message in context: http://grinder.996249.n3.nabble.com/Incorrect-timings-in-Grinder-tp8978p8982.html
Sent from the Grinder - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/