Timer

[Christian Sterzl <ch...@pdts.at>]

Hello

I have problems using timer.

In my Application I need to need measure response time of a certain transaction
called T (5 Transactions) when 100 user are logged in. T should be started by 50
Users in a Minute (T starts when T1 is called. I have to measure response times
of T1 to T5). So I made following test plan:

Counter
Thread Group (100/100 ramp-up/1)
---HTTP Request(Load LoginPage)
---HTTP Request(Login)
---IF Counter>50
------Simple Controller
---------Synchronizing Timer(50)
------HTTP Request(T1)
---------Constant Throughput Timer(50/all active threads)
------HTTP Request(T2)
------HTTP Request(T3)
------HTTP Request(T4)
------HTTP Request(T5)
---HTTP Request(Logout)
------Synchronizing Timer(100)

If all 50 Users made T, every User should log out.

It's like my First Synchronizing Timer got ignored. Particular it runs, that the
first 50 Users are logging in and logging out the next moment. All after coming
users are going through T1 to T5. But those users are never logging out, cause
they are not getting 100.

Does anyone have experience of a similiar test. Instead of the constant
throughput timer, a constant timer is also possible, if i can say for every
thread wait a second, before going the next thread into request T1. But i'm
getting really headache of this synch timer.

regards

chris


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

Re: Timer

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

Unless there is also a sampler in the Logic controller ... but point
taken; the documentation is misleading.

S.
On 28/11/05, Bruno Charloup <bc...@jouve.fr> wrote:
> There is a problem in the JMeter document, in the section 18.6 about Timers.
> It is written " ... To apply a timer after a sampler, either add it to the
> next sampler, or add it as the child of a simple logic controller
> immediately after the sampler."
> Only the 1st proposition works, and it works fine.
>
>
> -----Message d'origine-----
> De : sebb [mailto:sebbaz@gmail.com]
> Envoyé : vendredi 25 novembre 2005 18:27
> À : JMeter Users List
> Objet : Re: Timer
>
> On 24/11/05, Christian Sterzl <ch...@pdts.at> wrote:
> > Hello
> >
> > I have problems using timer.
> >
> > In my Application I need to need measure response time of a certain
> > transaction called T (5 Transactions) when 100 user are logged in. T
> > should be started by 50 Users in a Minute (T starts when T1 is called.
> > I have to measure response times of T1 to T5). So I made following test
> plan:
> >
> > Counter
> > Thread Group (100/100 ramp-up/1)
> > ---HTTP Request(Load LoginPage)
> > ---HTTP Request(Login)
> > ---IF Counter>50
> > ------Simple Controller
> > ---------Synchronizing Timer(50)
>
> > ------HTTP Request(T1)
> > ---------Constant Throughput Timer(50/all active threads) ------HTTP
> > Request(T2) ------HTTP Request(T3) ------HTTP Request(T4) ------HTTP
> > Request(T5) ---HTTP Request(Logout) ------Synchronizing Timer(100)
> >
> > If all 50 Users made T, every User should log out.
> >
> > It's like my First Synchronizing Timer got ignored. Particular it
> > runs, that the
>
> Config items, Timers, Pre- and Post-Processors are only executed when a
> sampler is processed.
>
> > first 50 Users are logging in and logging out the next moment. All
> > after coming users are going through T1 to T5. But those users are
> > never logging out, cause they are not getting 100.
> >
> > Does anyone have experience of a similiar test. Instead of the
> > constant throughput timer, a constant timer is also possible, if i can
> > say for every thread wait a second, before going the next thread into
> > request T1. But i'm getting really headache of this synch timer.
> >
> > regards
> >
> > chris
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

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

RE: Timer

[Bruno Charloup <bc...@jouve.fr>]

There is a problem in the JMeter document, in the section 18.6 about Timers.
It is written " ... To apply a timer after a sampler, either add it to the
next sampler, or add it as the child of a simple logic controller
immediately after the sampler."
Only the 1st proposition works, and it works fine.


-----Message d'origine-----
De : sebb [mailto:sebbaz@gmail.com] 
Envoyé : vendredi 25 novembre 2005 18:27
À : JMeter Users List
Objet : Re: Timer

On 24/11/05, Christian Sterzl <ch...@pdts.at> wrote:
> Hello
>
> I have problems using timer.
>
> In my Application I need to need measure response time of a certain 
> transaction called T (5 Transactions) when 100 user are logged in. T 
> should be started by 50 Users in a Minute (T starts when T1 is called. 
> I have to measure response times of T1 to T5). So I made following test
plan:
>
> Counter
> Thread Group (100/100 ramp-up/1)
> ---HTTP Request(Load LoginPage)
> ---HTTP Request(Login)
> ---IF Counter>50
> ------Simple Controller
> ---------Synchronizing Timer(50)

> ------HTTP Request(T1)
> ---------Constant Throughput Timer(50/all active threads) ------HTTP 
> Request(T2) ------HTTP Request(T3) ------HTTP Request(T4) ------HTTP 
> Request(T5) ---HTTP Request(Logout) ------Synchronizing Timer(100)
>
> If all 50 Users made T, every User should log out.
>
> It's like my First Synchronizing Timer got ignored. Particular it 
> runs, that the

Config items, Timers, Pre- and Post-Processors are only executed when a
sampler is processed.

> first 50 Users are logging in and logging out the next moment. All 
> after coming users are going through T1 to T5. But those users are 
> never logging out, cause they are not getting 100.
>
> Does anyone have experience of a similiar test. Instead of the 
> constant throughput timer, a constant timer is also possible, if i can 
> say for every thread wait a second, before going the next thread into 
> request T1. But i'm getting really headache of this synch timer.
>
> regards
>
> chris
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

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



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

Re: Timer

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

On 24/11/05, Christian Sterzl <ch...@pdts.at> wrote:
> Hello
>
> I have problems using timer.
>
> In my Application I need to need measure response time of a certain transaction
> called T (5 Transactions) when 100 user are logged in. T should be started by 50
> Users in a Minute (T starts when T1 is called. I have to measure response times
> of T1 to T5). So I made following test plan:
>
> Counter
> Thread Group (100/100 ramp-up/1)
> ---HTTP Request(Load LoginPage)
> ---HTTP Request(Login)
> ---IF Counter>50
> ------Simple Controller
> ---------Synchronizing Timer(50)

> ------HTTP Request(T1)
> ---------Constant Throughput Timer(50/all active threads)
> ------HTTP Request(T2)
> ------HTTP Request(T3)
> ------HTTP Request(T4)
> ------HTTP Request(T5)
> ---HTTP Request(Logout)
> ------Synchronizing Timer(100)
>
> If all 50 Users made T, every User should log out.
>
> It's like my First Synchronizing Timer got ignored. Particular it runs, that the

Config items, Timers, Pre- and Post-Processors are only executed when
a sampler is processed.

> first 50 Users are logging in and logging out the next moment. All after coming
> users are going through T1 to T5. But those users are never logging out, cause
> they are not getting 100.
>
> Does anyone have experience of a similiar test. Instead of the constant
> throughput timer, a constant timer is also possible, if i can say for every
> thread wait a second, before going the next thread into request T1. But i'm
> getting really headache of this synch timer.
>
> regards
>
> chris
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

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