On 14 September 2011 19:36, Deepak Shetty <shet...@gmail.com> wrote: > then you are on httpclient 3.1
Perhaps we are talking about different things. JMeter 2.4 supports 2 different HTTP Samplers: - HTTP Request (this is Java) - HTTP Request HTTPClient (this is HttpClient 3.1) which of these is being used? > On Wed, Sep 14, 2011 at 11:34 AM, E S <electric.or.sh...@gmail.com> wrote: > >> I am using JMeter 2.4 r961953. >> >> On Wed, Sep 14, 2011 at 1:18 PM, Deepak Shetty <shet...@gmail.com> wrote: >> > if you are using JMeter 2.5 on the HTTP Sampler , there is a drop down >> named >> > implementation >> > >> > On Wed, Sep 14, 2011 at 11:06 AM, E S <electric.or.sh...@gmail.com> >> wrote: >> > >> >> So how do I tell which HttpClient I am using? Is there a config option >> >> for that somewhere? I looked in jmeter.conf and saw some comments >> >> related to http client 3.x but nothing that looked very definitive. >> >> >> >> In terms of running out of ephemeral ports, I guess my options are to >> >> try to increase the port range, lower the TIME_WAIT value so the ports >> >> are freed up faster, or use distributed load generation. Other >> >> options? >> >> >> >> >> >> On Wed, Sep 14, 2011 at 12:32 PM, sebb <seb...@gmail.com> wrote: >> >> > On 14 September 2011 17:51, E S <electric.or.sh...@gmail.com> wrote: >> >> >> I'm seeing a jar file in the lib directory called >> >> >> commons-httpclient-3.1, so I assume I'm using HttpClient 3.1. >> >> > >> >> > Not necessarily. There were two Http Sampler implementations in JMeter >> >> 2.4. >> >> > These are merged in JMeter 2.5, which has a drop-down list for the >> >> > implementation. >> >> > >> >> >> What do you mean when you say it might be related to timing? >> >> > >> >> > Depending on timing, the OS may have had time to free up the resources >> or >> >> not. >> >> > >> >> >> On Wed, Sep 14, 2011 at 3:45 AM, sebb <seb...@gmail.com> wrote: >> >> >>> >> >> >>> On 14 September 2011 04:51, E S <electric.or.sh...@gmail.com> >> wrote: >> >> >>> > 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? >> >> >>> >> >> >>> If everything else in the plan is the same, then it must just be >> >> >>> timing-related, because the timers just wait as needed. >> >> >>> >> >> >>> If the box is near the limit of ports, then changes in timing might >> >> >>> have an effect. >> >> >>> >> >> >>> Which HTTP sampler are you using? >> >> >>> HttpClient4 (in version 2.5; fixed but not yet released) has an >> >> >>> unfortunate bug that means it uses up lots of connections; best to >> use >> >> >>> HttpClient3.1. >> >> >>> >> >> >>> > 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 >> >> >>> >> >> >> >>> >> >> >> >>> > >> >> >>> >> >> >>> >> --------------------------------------------------------------------- >> >> >>> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> >> >>> For additional commands, e-mail: >> jmeter-user-h...@jakarta.apache.org >> >> >>> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> >> >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> >> >> >> >> >> >> > >> >> > --------------------------------------------------------------------- >> >> > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> >> > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> > >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> >> >> >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org >> For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
