> Is it possible to vary the delay between consecutive sampler requests?
I basically wanted to vary timer delay to simulate transaction surges...
the last delay would sleep the thread for an hour before waking it up
again.
I don't know if that can be done, but here's a note on a workaround I
found:
Add Sampler/Java Request/Sleep Test
Then set Sleep Time = number of milliseconds we want the thread to
delay.
With regards,
Sonam Chauhan
--
Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED]
> -----Original Message-----
> From: Sonam Chauhan [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 8 January 2004 9:45 AM
> To: 'JMeter Users List'
> Subject: RE: Timer wierdness
>
> > script vs. configuration-tree behaviour: timers do not 'execute' in
> the
> > way samplers and controllers do, but they apply to every sampler in
> > their same controller or any subcontroller thereafter.
>
> Thanks Jordi - that explains everything.
>
> Is it possible to vary the delay between consecutive sampler requests?
> E.g.:
> ---Delay 20 ms
> ---HTTP Sampler 1
> ---Delay 2000000 ms
> ---HTTP Sampler 2
> ---Delay 20 ms
> ---HTTP Sampler 3
>
> I read the documentation, and couldn't figure out a way for a timer to
> "override" a previous timer in the same controller.
>
> With regards,
> Sonam Chauhan
> --
> Corporate Express Australia Ltd.
> Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED]
>
>
> > -----Original Message-----
> > From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, 8 January 2004 5:03 AM
> > To: JMeter Users List
> > Subject: Re: Timer wierdness
> >
> > Hi Sonam,
> >
> > this is one more occurence of a common misunderstanding -- the
famous
> > script vs. configuration-tree behaviour: timers do not 'execute' in
> the
> > way samplers and controllers do, but they apply to every sampler in
> > their same controller or any subcontroller thereafter. So if you
have
> 5
> > requests and place one timer before each of them, you get 5 times
the
> > delay before each request. Leave only 1 of the timers and you'll be
> set.
> >
> > BTW, your 2nd measurement is probably in error: the real value is
more
> > like 2500.
> >
> > Hope this helps,
> >
> > Jordi.
> >
> > P.S.: we should do something to avoid this confusion. Is took me a
> loot
> > of time to understand what was going on with the timers.
> >
> > En/na Sonam Chauhan ha escrit:
> > > Has anyone seen timers taking longer than they should? I have a
JMX
> that
> > > makes 5 HTTP requests with Uniform Random Timer inserting a delay
in
> > between
> > > each request.
> > >
> > > Setting the timer's random delay to 0, and varying the timer's
> constant
> > > delay, I got the following figures for the real delay of each
timer.
> > > (numbers adjusted for page load delays.)
> > >
> > > Constant delay Approx. actual delay.
> > > (ms) (ms)
> > > =======================================
> > > 0 0
> > > 500 2000
> > > 1000 5000
> > > 1500 7500
> > > 2000 10000
> > > =======================================
> > >
> > > In this case, the timer actually seem to take 4-5 times as long.
> > >
> > > With regards,
> > > Sonam Chauhan
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
