To answer your question, on the 6000 req/sec tests where this is no throughput timer, it's about what you would expect, around 30 ms for the average request. So that means each thread can do about 33 request per second and if you have 200 threads that's roughly 6000 requests per second.
I did just notice something significant though. I am getting errors on the tests that use the constant throughput timer. Some of the requests (usually around 10%) give the following error: "Response code: Non HTTP response code: java.net.NoRouteToHostException Response message: Non HTTP response message: Cannot assign requested address" >From what I've researched and the evidence I've gathered on the JMeter box, I'm running out of ephemeral ports. I find this strange though since it doesn't happen when I run without the throughput timer. Shouldn't a be running out of ports either way? What is the timer doing that makes me use more ports? On Tue, Sep 13, 2011 at 3:11 AM, Oliver Lloyd <oliver_ll...@hotmail.com>wrote: > What are the response times when you run these tests? > > ----- > http://www.http503.com/ > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Constant-throughput-timer-not-giving-expected-results-tp4784904p4797538.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
