Re: Constant throughput timer not giving expected results
Ah, you're right. I'm using HTTP Request. I had not even noticed the HTTPClient sampler. Sorry for the confusion. On Wed, Sep 14, 2011 at 2:19 PM, sebb wrote: > On 14 September 2011 19:36, Deepak Shetty 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 wrote: >> >>> I am using JMeter 2.4 r961953. >>> >>> On Wed, Sep 14, 2011 at 1:18 PM, Deepak Shetty 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 >>> 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 wrote: >>> >> > On 14 September 2011 17:51, E S 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 wrote: >>> >> >>> >>> >> >>> On 14 September 2011 04:51, E S >>> 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 >>> >> >>> >>> >> >> >>> >> >> --
Re: Constant throughput timer not giving expected results
On 14 September 2011 19:36, Deepak Shetty 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 wrote: > >> I am using JMeter 2.4 r961953. >> >> On Wed, Sep 14, 2011 at 1:18 PM, Deepak Shetty 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 >> 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 wrote: >> >> > On 14 September 2011 17:51, E S 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 wrote: >> >> >>> >> >> >>> On 14 September 2011 04:51, E S >> 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 >> >> >> >> >> >> >> >> > >> >> > -
Re: Constant throughput timer not giving expected results
then you are on httpclient 3.1 On Wed, Sep 14, 2011 at 11:34 AM, E S wrote: > I am using JMeter 2.4 r961953. > > On Wed, Sep 14, 2011 at 1:18 PM, Deepak Shetty 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 > 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 wrote: > >> > On 14 September 2011 17:51, E S 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 wrote: > >> >>> > >> >>> On 14 September 2011 04:51, E S > 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
Re: Constant throughput timer not giving expected results
I am using JMeter 2.4 r961953. On Wed, Sep 14, 2011 at 1:18 PM, Deepak Shetty 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 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 wrote: >> > On 14 September 2011 17:51, E S 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 wrote: >> >>> >> >>> On 14 September 2011 04:51, E S 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
Re: Constant throughput timer not giving expected results
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 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 wrote: > > On 14 September 2011 17:51, E S 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 wrote: > >>> > >>> On 14 September 2011 04:51, E S 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 > >
Re: Constant throughput timer not giving expected results
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 wrote: > On 14 September 2011 17:51, E S 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 wrote: >>> >>> On 14 September 2011 04:51, E S 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 >>> > 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
Re: Constant throughput timer not giving expected results
On 14 September 2011 17:51, E S 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 wrote: >> >> On 14 September 2011 04:51, E S 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 >> > 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
Re: Constant throughput timer not giving expected results
I'm seeing a jar file in the lib directory called commons-httpclient-3.1, so I assume I'm using HttpClient 3.1. What do you mean when you say it might be related to timing? On Wed, Sep 14, 2011 at 3:45 AM, sebb wrote: > > On 14 September 2011 04:51, E S 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 > > 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
Re: Constant throughput timer not giving expected results
On 14 September 2011 04:51, E S 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 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
Re: Constant throughput timer not giving expected results
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 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 > >
Re: Constant throughput timer not giving expected results
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
Re: Constant throughput timer not giving expected results
Well I did some more testing and I have to say that I'm still confused. All I can figure is that I am misunderstanding how the constant throughput timer works. I was able to configure the throughput timer to get the same results as I did without it (6000 req/sec) but I had to set the total throughput value on the timer to be really high (about 2,000,000 req/min). I would think the number should be around 360,000 but for some reason that's not enough. This is using the "all active threads in the current thread group" mode. I tried using the "this thread only" mode. I set the test up with 200 threads and the throughput timer to have each thread run at 1800 req/min. According to my understanding, that is 200 threads each pumping out 30 requests per second for a total of 6000 requests per second. Under this configuration my total throughput was only 1400 requests per second. I had to jack up the timer's setting to 22,000 req/min to get the proper throughput. I don't get this. Clearly the server is capable of providing the throughput that I'm looking for. Why do I have to set the timers in such weird ways to get the throughput to the desired level? On Fri, Sep 9, 2011 at 6:57 AM, sebb wrote: > On 9 September 2011 04:31, E S wrote: > > I'm having some trouble getting the Constant Throughput Timer to work the > > way I want in certain cases. > > > > I have a single thread group of 100 threads, all of which are requesting > the > > same resource over and over for 1 minute. > > > > I attached a Constant Throughput Timer on the thread group and ran a > series > > tests with the throughput throttled at higher and higher levels such as > > 6000, 8000, 1, etc. Here is a table showing the throughput timer > > settings and the actual number of requests that the server under test > > responded to: > > > > thruput-setting..actual-requests-served > > 36,000.36,000 > > 48,000.48,000 > > 60,000.60,000 > > 72,000.60,000 > > 84,000.60,000 > > > > So it looks like the server under test simply can't respond to more than > > 60,000 requests per minute right? However, when I disable the throughput > > timer I get way higher throughput, something like 350,000 requests per > > minute. What's going on here? Why is the throughput timer giving me these > > results? Is it possible that JMeter is spending so much time trying to > keep > > the throughput at the right level that it doesn't have enough cycles left > to > > dedicate to actual requests? I tried distributing the load across > multiple > > load generators but it didn't seem to help. > > > > The results above have the throughput timer configured using Calculate > > Throughput based on = "all active threads in current thread group". I > tried > > changing this to "all active threads in current thread group (shared)" > and I > > get the maximum results of 350,000 as if the throughput timer was not > even > > there. I must admit I don't understand the difference between the two > > settings, but neither result sounds right. > > > > Any ideas about this? > > Create a test plan using the Java Sampler with timer settings that > correspond to your server. > > Run a test with CTT disabled and check you get the desired throughput > (use Summary Listener). > > You can then experiment with the CTT without needing to take server > and network behaviour into account. > > - > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
Re: Constant throughput timer not giving expected results
On 9 September 2011 04:31, E S wrote: > I'm having some trouble getting the Constant Throughput Timer to work the > way I want in certain cases. > > I have a single thread group of 100 threads, all of which are requesting the > same resource over and over for 1 minute. > > I attached a Constant Throughput Timer on the thread group and ran a series > tests with the throughput throttled at higher and higher levels such as > 6000, 8000, 1, etc. Here is a table showing the throughput timer > settings and the actual number of requests that the server under test > responded to: > > thruput-setting..actual-requests-served > 36,000.36,000 > 48,000.48,000 > 60,000.60,000 > 72,000.60,000 > 84,000.60,000 > > So it looks like the server under test simply can't respond to more than > 60,000 requests per minute right? However, when I disable the throughput > timer I get way higher throughput, something like 350,000 requests per > minute. What's going on here? Why is the throughput timer giving me these > results? Is it possible that JMeter is spending so much time trying to keep > the throughput at the right level that it doesn't have enough cycles left to > dedicate to actual requests? I tried distributing the load across multiple > load generators but it didn't seem to help. > > The results above have the throughput timer configured using Calculate > Throughput based on = "all active threads in current thread group". I tried > changing this to "all active threads in current thread group (shared)" and I > get the maximum results of 350,000 as if the throughput timer was not even > there. I must admit I don't understand the difference between the two > settings, but neither result sounds right. > > Any ideas about this? Create a test plan using the Java Sampler with timer settings that correspond to your server. Run a test with CTT disabled and check you get the desired throughput (use Summary Listener). You can then experiment with the CTT without needing to take server and network behaviour into account. - To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
Re: Constant throughput timer not giving expected results
Also, keep in mind. 100 threads trying to achieve 60,000 requests a second means that each atomic process must complete within 100ms - that includes not only the request /response but also JMeter's processing time. 100ms isn't that long, you might find you are limited by JM or by the time your request takes to respond - either way, if you want more throughput you'll probably need more threads. - http://www.http503.com/ -- View this message in context: http://jmeter.512774.n5.nabble.com/Constant-throughput-timer-not-giving-expected-results-tp4784904p4785825.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
Re: Constant throughput timer not giving expected results
I find that it is a lot simpler to Calculate Throughput based on 'This Thread Only'. That option basically means if I set the CTT to a value of 60 and only have 1 thread then I will get a throughput of 1 request per second. If I have 2 threads I will get 2 requests a second, 3 threads = 3tps, etc. You still need to factor in concurrency when planning this as well as the fact that longer response times will potentially prevent the CTT from achieving what you tell it to. In direct answer to your question, yes, it sounds like you have a bottleneck of some sort. The reason why it stops at 60,000 and not some other value is probably just because your response times increase and this slows down the throughput. It might be that a higher value is possible under a different configuration (more threads trying more often) but really, the more important question is why are the response times increasing! If you change the test to be more aggressive then you actually make it harder to identify the problem - slow and gradual is, generally, better for finding breakpoints compared to hard and fast. - http://www.http503.com/ -- View this message in context: http://jmeter.512774.n5.nabble.com/Constant-throughput-timer-not-giving-expected-results-tp4784904p4785802.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
