Re: Constant Throughput Timer

[Patrick Li <dr...@gmail.com>]

OK, I think I get it now.  So, this should be independent of the number of
concurrent threads too I guess since the timer should "control" all the
active threads and put them on hold as needed in order to reach the desired
throughput?  i.e. 50 threads and 100 threads should make little or no
difference if I set a throughput which is achievable.

Regards

Liang

On Wed, Mar 31, 2010 at 10:12 PM, sebb <se...@gmail.com> wrote:

> On 31/03/2010, Patrick Li <dr...@gmail.com> wrote:
> > Hi,
> >
> >  Thanks, that makes sense.  One more question, is it possible to achieve
> that
> >  (continue sending requests regardless of server capacity) with some
> other
> >  sort of timer or approach?
>
> As I wrote, JMeter waits for the response before it will send any
> further request.
> To clarify - each thread waits for a response to its request before
> continuing to process the other elements in the test.
>
> It does not make sense to me to continue sending more requests if the
> server is already struggling to keep up.

Re: Constant Throughput Timer

[sebb <se...@gmail.com>]

On 03/04/2010, Patrick Li <dr...@gmail.com> wrote:
> OK, I think I get it now.  So, this should be independent of the number of
>  concurrent threads too I guess since the timer should "control" all the
>  active threads and put them on hold as needed in order to reach the desired
>  throughput?  i.e. 50 threads and 100 threads should make little or no
>  difference if I set a throughput which is achievable.

Yes, that's correct. The number of threads is not all that important
so long as there are sufficient to generate enough load - and not so
many that they cause problems for the JMeter host.

>  Regards
>
>  Liang
>
>
>  On Wed, Mar 31, 2010 at 10:12 PM, sebb <se...@gmail.com> wrote:
>
>  > On 31/03/2010, Patrick Li <dr...@gmail.com> wrote:
>  > > Hi,
>  > >
>  > >  Thanks, that makes sense.  One more question, is it possible to achieve
>  > that
>  > >  (continue sending requests regardless of server capacity) with some
>  > other
>  > >  sort of timer or approach?
>  >
>  > As I wrote, JMeter waits for the response before it will send any
>  > further request.
>  > To clarify - each thread waits for a response to its request before
>  > continuing to process the other elements in the test.
>  >
>  > It does not make sense to me to continue sending more requests if the
>  > server is already struggling to keep up.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org