Re: Test Duration
On Wed, Mar 1, 2017 at 10:57 PM, Philippe Mouawad < philippe.moua...@gmail.com> wrote: > Hello, > Note that as of current nightly build, there remain a "problem" with Test > Action. > If it is set in Pause mode with a duration that will last beyond test end, > this is not detected. > I opened bug: > https://bz.apache.org/bugzilla/show_bug.cgi?id=60797 > Issue fixed now with non regression tests added. Tests of nightly (available on Jenkins in 15 minutes) and feedback welcome : http://jmeter.apache.org/nightly.html Thanks > > > Regarding timers, this has been fixed in 3.1: > https://bz.apache.org/bugzilla/show_bug.cgi?id=60049 > > Regards > Philippe > -- Cordialement. Philippe Mouawad.
Re: Test Duration
On Wed, Mar 1, 2017 at 9:48 PM, Felix Schumacher <felix.schumacher@
internetallee.de> wrote:
> Am 01.03.2017 um 20:06 schrieb Philippe Mouawad:
>
>> On Wednesday, March 1, 2017, Stuart Kenworthy <stuart.kenwor...@bjss.com>
>> wrote:
>>
>> Many people are still using 2.13 which Is why I mentioned it.
>>>
>>> However there is still a potential problem, duration does not interrupt
>>> timers or test action waits.
>>>
>> It does interrupt them since 3.1 I think it not 3.0.
>> This bug was fixed.
>>
>>
>> Also if you have samplers that are currently awaiting a response, it waits
>>> until the response before terminating.
>>>
>> yes, that seems correct to me.
>> Intereupting them would lead to a high error rate on last samples.
>> But you can force a stop if you want.
>>
> Maybe we could tell the listeners to ignore anything after the scheduler
> says the test is finished. That way we would get not errors by interrupting
> the "stuck" samplers.
>
Sounds interesting. Is there a chance we get "bug reports" about samplers
that were not written ? (those ones ?)
>
> Felix
>
>
>> This means if you have a 10 minute wait, via timer or test action, in your
>>> test plan and one if the threads is in the timer or test action, or your
>>> sampler is currently waiting to timeout, you have to wait for that to
>>> finish after the duration ends.
>>>
>> Yes for timeout.
>> No more for timers.
>>
>>
>> I understand this is by design and is also present in the UI but it does
>>> cause problems when running real world user journeys.
>>>
>> If you still experience issues in 3.1, please raise a bugzilla bug so that
>> we fix it.
>> Attach a sample test plan and be as precise as possible.
>>
>> Not a major problem but something a lot of people fall into.
>>>
>>
>> Yes, I falled into it myself when using Throughput timer, that's why it
>> was
>> fixed.
>> Unfortunately we cannot fix bugs we're not aware of :)
>>
>> -Original Message-
>>> From: Philippe Mouawad [mailto:philippe.moua...@gmail.com
>>> <javascript:;>]
>>> Sent: 01 March 2017 18:04
>>> To: JMeter Users List <user@jmeter.apache.org <javascript:;>>
>>> Subject: Re: Test Duration
>>>
>>> Hello,
>>> The methods described by Antonio and Sebb work perfectly well.
>>> If you have any issue, please provide more details and an example test
>>> plan.
>>>
>>> No need to switch to old 2.13 for this.
>>>
>>> Regards
>>>
>>> On Wednesday, March 1, 2017, Stuart Kenworthy <stuart.kenwor...@bjss.com
>>> <javascript:;>>
>>>
>>> wrote:
>>>
>>> Wow I take that back, it now seems that schedule in v3.1 does seem to
>>>> do what you expect. May want to test properly if using 2.13.
>>>>
>>>> -Original Message-
>>>> From: Stuart Kenworthy [mailto:stuart.kenwor...@bjss.com <javascript:;>
>>>> <javascript:;>]
>>>> Sent: 01 March 2017 16:33
>>>> To: JMeter Users List <user@jmeter.apache.org <javascript:;>
>>>>
>>> <javascript:;>>
>>>
>>>> Subject: RE: Test Duration
>>>>
>>>> Does this actually work? In my experience, running a scheduler in
>>>> command line does not work as expected, or at all.
>>>>
>>>> -Original Message-
>>>> From: Antonio Gomes Rodrigues [mailto:ra0...@gmail.com <javascript:;>
>>>>
>>> <javascript:;>]
>>>
>>>> Sent: 01 March 2017 16:30
>>>> To: JMeter Users List <user@jmeter.apache.org <javascript:;>
>>>>
>>> <javascript:;>>
>>>
>>>> Subject: Re: Test Duration
>>>>
>>>> Put ${__P(RUNTIME,100) in the "Thread Group" element in "Duration
>>>> (seconds)" input
>>>>
>>>> And when you run JMeter, use -JRUNTIME=99 in the command line
>>>>
>>>> Instead of 99, put the desired test duration in seconds
>>>>
>>>> 2017-03-01 17:25 GMT+01:00 Stuart Kenworthy <stuart.kenwor...@bjss.com
>>>>
>>> <javascript:;>
>>>
>>>> <javascript:;>>:
>>>>
>>>> And how would this be used to control run time within the script
>>>>>
>>
Re: Test Duration
Am 01.03.2017 um 20:06 schrieb Philippe Mouawad:
On Wednesday, March 1, 2017, Stuart Kenworthy <stuart.kenwor...@bjss.com>
wrote:
Many people are still using 2.13 which Is why I mentioned it.
However there is still a potential problem, duration does not interrupt
timers or test action waits.
It does interrupt them since 3.1 I think it not 3.0.
This bug was fixed.
Also if you have samplers that are currently awaiting a response, it waits
until the response before terminating.
yes, that seems correct to me.
Intereupting them would lead to a high error rate on last samples.
But you can force a stop if you want.
Maybe we could tell the listeners to ignore anything after the scheduler
says the test is finished. That way we would get not errors by
interrupting the "stuck" samplers.
Felix
This means if you have a 10 minute wait, via timer or test action, in your
test plan and one if the threads is in the timer or test action, or your
sampler is currently waiting to timeout, you have to wait for that to
finish after the duration ends.
Yes for timeout.
No more for timers.
I understand this is by design and is also present in the UI but it does
cause problems when running real world user journeys.
If you still experience issues in 3.1, please raise a bugzilla bug so that
we fix it.
Attach a sample test plan and be as precise as possible.
Not a major problem but something a lot of people fall into.
Yes, I falled into it myself when using Throughput timer, that's why it was
fixed.
Unfortunately we cannot fix bugs we're not aware of :)
-Original Message-
From: Philippe Mouawad [mailto:philippe.moua...@gmail.com <javascript:;>]
Sent: 01 March 2017 18:04
To: JMeter Users List <user@jmeter.apache.org <javascript:;>>
Subject: Re: Test Duration
Hello,
The methods described by Antonio and Sebb work perfectly well.
If you have any issue, please provide more details and an example test
plan.
No need to switch to old 2.13 for this.
Regards
On Wednesday, March 1, 2017, Stuart Kenworthy <stuart.kenwor...@bjss.com
<javascript:;>>
wrote:
Wow I take that back, it now seems that schedule in v3.1 does seem to
do what you expect. May want to test properly if using 2.13.
-Original Message-
From: Stuart Kenworthy [mailto:stuart.kenwor...@bjss.com <javascript:;>
<javascript:;>]
Sent: 01 March 2017 16:33
To: JMeter Users List <user@jmeter.apache.org <javascript:;>
<javascript:;>>
Subject: RE: Test Duration
Does this actually work? In my experience, running a scheduler in
command line does not work as expected, or at all.
-Original Message-
From: Antonio Gomes Rodrigues [mailto:ra0...@gmail.com <javascript:;>
<javascript:;>]
Sent: 01 March 2017 16:30
To: JMeter Users List <user@jmeter.apache.org <javascript:;>
<javascript:;>>
Subject: Re: Test Duration
Put ${__P(RUNTIME,100) in the "Thread Group" element in "Duration
(seconds)" input
And when you run JMeter, use -JRUNTIME=99 in the command line
Instead of 99, put the desired test duration in seconds
2017-03-01 17:25 GMT+01:00 Stuart Kenworthy <stuart.kenwor...@bjss.com
<javascript:;>
<javascript:;>>:
And how would this be used to control run time within the script
itself?
-Original Message-
From: sebb [mailto:seb...@gmail.com <javascript:;> <javascript:;>]
Sent: 01 March 2017 16:24
To: JMeter Users List <user@jmeter.apache.org <javascript:;>
<javascript:;>>
Subject: Re: Test Duration
Simpler to use a property reference, for example:
${__P(RUNTIME,100)
Then use -JRUNTIME=99 on the command line
On 1 March 2017 at 16:18, Antonio Gomes Rodrigues <ra0...@gmail.com
<javascript:;>
<javascript:;>>
wrote:
Hi,
Put a JMeter variable in the "Thread Group" element in "Duration
(seconds)"
input
And use -J command line option to define it
Antonio
2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com
<javascript:;>
<javascript:;>>:
This is exactly the problem that came up in our test organization.
We couldn't figure it out (running jmeter for a specified time
from the command line) so, our solution is to have a shell script
start jmeter and, after the required time, calls shutdown.sh. The
whole thing works using nohup and works like a charm.
Bo
*Bohdan L. Bodnar*
Lead Performance Engineer
1-312-871-5163 <(312)%20871-5163>
--
*E-mail:* *bbod...@us.ibm.com <javascript:;> <javascript:;>* <
bbod...@us.ibm.com <javascript:;>
<javascript:;>>
222 South Riverside Plaza
Chicago, IL 60606
United States
[image: Inactive hide details for Stuart Barlow ---03/01/2017
10:04:07 AM---Hi. Is there a way to define the duration a test
should run]Stuart Barlow ---03/01/2017 10:04:07 AM---Hi
Re: Test Duration
On Wednesday, March 1, 2017, Stuart Kenworthy <stuart.kenwor...@bjss.com>
wrote:
> Many people are still using 2.13 which Is why I mentioned it.
>
> However there is still a potential problem, duration does not interrupt
> timers or test action waits.
It does interrupt them since 3.1 I think it not 3.0.
This bug was fixed.
>
> Also if you have samplers that are currently awaiting a response, it waits
> until the response before terminating.
yes, that seems correct to me.
Intereupting them would lead to a high error rate on last samples.
But you can force a stop if you want.
>
> This means if you have a 10 minute wait, via timer or test action, in your
> test plan and one if the threads is in the timer or test action, or your
> sampler is currently waiting to timeout, you have to wait for that to
> finish after the duration ends.
Yes for timeout.
No more for timers.
>
> I understand this is by design and is also present in the UI but it does
> cause problems when running real world user journeys.
If you still experience issues in 3.1, please raise a bugzilla bug so that
we fix it.
Attach a sample test plan and be as precise as possible.
>
> Not a major problem but something a lot of people fall into.
Yes, I falled into it myself when using Throughput timer, that's why it was
fixed.
Unfortunately we cannot fix bugs we're not aware of :)
>
> -Original Message-
> From: Philippe Mouawad [mailto:philippe.moua...@gmail.com <javascript:;>]
> Sent: 01 March 2017 18:04
> To: JMeter Users List <user@jmeter.apache.org <javascript:;>>
> Subject: Re: Test Duration
>
> Hello,
> The methods described by Antonio and Sebb work perfectly well.
> If you have any issue, please provide more details and an example test
> plan.
>
> No need to switch to old 2.13 for this.
>
> Regards
>
> On Wednesday, March 1, 2017, Stuart Kenworthy <stuart.kenwor...@bjss.com
> <javascript:;>>
> wrote:
>
> > Wow I take that back, it now seems that schedule in v3.1 does seem to
> > do what you expect. May want to test properly if using 2.13.
> >
> > -Original Message-
> > From: Stuart Kenworthy [mailto:stuart.kenwor...@bjss.com <javascript:;>
> > <javascript:;>]
> > Sent: 01 March 2017 16:33
> > To: JMeter Users List <user@jmeter.apache.org <javascript:;>
> <javascript:;>>
> > Subject: RE: Test Duration
> >
> > Does this actually work? In my experience, running a scheduler in
> > command line does not work as expected, or at all.
> >
> > -Original Message-
> > From: Antonio Gomes Rodrigues [mailto:ra0...@gmail.com <javascript:;>
> <javascript:;>]
> > Sent: 01 March 2017 16:30
> > To: JMeter Users List <user@jmeter.apache.org <javascript:;>
> <javascript:;>>
> > Subject: Re: Test Duration
> >
> > Put ${__P(RUNTIME,100) in the "Thread Group" element in "Duration
> > (seconds)" input
> >
> > And when you run JMeter, use -JRUNTIME=99 in the command line
> >
> > Instead of 99, put the desired test duration in seconds
> >
> > 2017-03-01 17:25 GMT+01:00 Stuart Kenworthy <stuart.kenwor...@bjss.com
> <javascript:;>
> > <javascript:;>>:
> >
> > > And how would this be used to control run time within the script
> itself?
> > >
> > > -Original Message-
> > > From: sebb [mailto:seb...@gmail.com <javascript:;> <javascript:;>]
> > > Sent: 01 March 2017 16:24
> > > To: JMeter Users List <user@jmeter.apache.org <javascript:;>
> <javascript:;>>
> > > Subject: Re: Test Duration
> > >
> > > Simpler to use a property reference, for example:
> > >
> > > ${__P(RUNTIME,100)
> > >
> > > Then use -JRUNTIME=99 on the command line
> > >
> > >
> > >
> > > On 1 March 2017 at 16:18, Antonio Gomes Rodrigues <ra0...@gmail.com
> <javascript:;>
> > <javascript:;>>
> > > wrote:
> > > > Hi,
> > > >
> > > > Put a JMeter variable in the "Thread Group" element in "Duration
> > > (seconds)"
> > > > input
> > > >
> > > > And use -J command line option to define it
> > > >
> > > > Antonio
> > > >
> > > > 2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com
> <javascript:;>
> > <javascript:;>>:
> > > >
> > > >> This is exactly the problem that came up in our test organization.
> > > >
RE: Test Duration
Many people are still using 2.13 which Is why I mentioned it.
However there is still a potential problem, duration does not interrupt timers
or test action waits.
Also if you have samplers that are currently awaiting a response, it waits
until the response before terminating.
This means if you have a 10 minute wait, via timer or test action, in your test
plan and one if the threads is in the timer or test action, or your sampler is
currently waiting to timeout, you have to wait for that to finish after the
duration ends.
I understand this is by design and is also present in the UI but it does cause
problems when running real world user journeys.
Not a major problem but something a lot of people fall into.
-Original Message-
From: Philippe Mouawad [mailto:philippe.moua...@gmail.com]
Sent: 01 March 2017 18:04
To: JMeter Users List <user@jmeter.apache.org>
Subject: Re: Test Duration
Hello,
The methods described by Antonio and Sebb work perfectly well.
If you have any issue, please provide more details and an example test plan.
No need to switch to old 2.13 for this.
Regards
On Wednesday, March 1, 2017, Stuart Kenworthy <stuart.kenwor...@bjss.com>
wrote:
> Wow I take that back, it now seems that schedule in v3.1 does seem to
> do what you expect. May want to test properly if using 2.13.
>
> -Original Message-
> From: Stuart Kenworthy [mailto:stuart.kenwor...@bjss.com
> <javascript:;>]
> Sent: 01 March 2017 16:33
> To: JMeter Users List <user@jmeter.apache.org <javascript:;>>
> Subject: RE: Test Duration
>
> Does this actually work? In my experience, running a scheduler in
> command line does not work as expected, or at all.
>
> -Original Message-
> From: Antonio Gomes Rodrigues [mailto:ra0...@gmail.com <javascript:;>]
> Sent: 01 March 2017 16:30
> To: JMeter Users List <user@jmeter.apache.org <javascript:;>>
> Subject: Re: Test Duration
>
> Put ${__P(RUNTIME,100) in the "Thread Group" element in "Duration
> (seconds)" input
>
> And when you run JMeter, use -JRUNTIME=99 in the command line
>
> Instead of 99, put the desired test duration in seconds
>
> 2017-03-01 17:25 GMT+01:00 Stuart Kenworthy <stuart.kenwor...@bjss.com
> <javascript:;>>:
>
> > And how would this be used to control run time within the script itself?
> >
> > -Original Message-----
> > From: sebb [mailto:seb...@gmail.com <javascript:;>]
> > Sent: 01 March 2017 16:24
> > To: JMeter Users List <user@jmeter.apache.org <javascript:;>>
> > Subject: Re: Test Duration
> >
> > Simpler to use a property reference, for example:
> >
> > ${__P(RUNTIME,100)
> >
> > Then use -JRUNTIME=99 on the command line
> >
> >
> >
> > On 1 March 2017 at 16:18, Antonio Gomes Rodrigues <ra0...@gmail.com
> <javascript:;>>
> > wrote:
> > > Hi,
> > >
> > > Put a JMeter variable in the "Thread Group" element in "Duration
> > (seconds)"
> > > input
> > >
> > > And use -J command line option to define it
> > >
> > > Antonio
> > >
> > > 2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com
> <javascript:;>>:
> > >
> > >> This is exactly the problem that came up in our test organization.
> > >> We couldn't figure it out (running jmeter for a specified time
> > >> from the command line) so, our solution is to have a shell script
> > >> start jmeter and, after the required time, calls shutdown.sh. The
> > >> whole thing works using nohup and works like a charm.
> > >>
> > >> Bo
> > >>
> > >>
> > >>
> > >> *Bohdan L. Bodnar*
> > >> Lead Performance Engineer
> > >> 1-312-871-5163 <(312)%20871-5163>
> > >> --
> > >> *E-mail:* *bbod...@us.ibm.com <javascript:;>* <bbod...@us.ibm.com
> <javascript:;>>
> > >> 222 South Riverside Plaza
> > >> Chicago, IL 60606
> > >> United States
> > >>
> > >> [image: Inactive hide details for Stuart Barlow ---03/01/2017
> > >> 10:04:07 AM---Hi. Is there a way to define the duration a test
> > >> should run]Stuart Barlow ---03/01/2017 10:04:07 AM---Hi. Is there
> > >> a way to define the duration a test should run via the command line?
> > >>
> > >> From: Stuart Barlow <stuart.bar...@gmail.com <javascript:;>>
> > >> To: <user@jmeter.apache
Re: Test Duration
Hello,
The methods described by Antonio and Sebb work perfectly well.
If you have any issue, please provide more details and an example test plan.
No need to switch to old 2.13 for this.
Regards
On Wednesday, March 1, 2017, Stuart Kenworthy <stuart.kenwor...@bjss.com>
wrote:
> Wow I take that back, it now seems that schedule in v3.1 does seem to do
> what you expect. May want to test properly if using 2.13.
>
> -Original Message-
> From: Stuart Kenworthy [mailto:stuart.kenwor...@bjss.com <javascript:;>]
> Sent: 01 March 2017 16:33
> To: JMeter Users List <user@jmeter.apache.org <javascript:;>>
> Subject: RE: Test Duration
>
> Does this actually work? In my experience, running a scheduler in command
> line does not work as expected, or at all.
>
> -Original Message-
> From: Antonio Gomes Rodrigues [mailto:ra0...@gmail.com <javascript:;>]
> Sent: 01 March 2017 16:30
> To: JMeter Users List <user@jmeter.apache.org <javascript:;>>
> Subject: Re: Test Duration
>
> Put ${__P(RUNTIME,100) in the "Thread Group" element in "Duration
> (seconds)" input
>
> And when you run JMeter, use -JRUNTIME=99 in the command line
>
> Instead of 99, put the desired test duration in seconds
>
> 2017-03-01 17:25 GMT+01:00 Stuart Kenworthy <stuart.kenwor...@bjss.com
> <javascript:;>>:
>
> > And how would this be used to control run time within the script itself?
> >
> > -Original Message-----
> > From: sebb [mailto:seb...@gmail.com <javascript:;>]
> > Sent: 01 March 2017 16:24
> > To: JMeter Users List <user@jmeter.apache.org <javascript:;>>
> > Subject: Re: Test Duration
> >
> > Simpler to use a property reference, for example:
> >
> > ${__P(RUNTIME,100)
> >
> > Then use -JRUNTIME=99 on the command line
> >
> >
> >
> > On 1 March 2017 at 16:18, Antonio Gomes Rodrigues <ra0...@gmail.com
> <javascript:;>>
> > wrote:
> > > Hi,
> > >
> > > Put a JMeter variable in the "Thread Group" element in "Duration
> > (seconds)"
> > > input
> > >
> > > And use -J command line option to define it
> > >
> > > Antonio
> > >
> > > 2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com
> <javascript:;>>:
> > >
> > >> This is exactly the problem that came up in our test organization.
> > >> We couldn't figure it out (running jmeter for a specified time from
> > >> the command line) so, our solution is to have a shell script start
> > >> jmeter and, after the required time, calls shutdown.sh. The whole
> > >> thing works using nohup and works like a charm.
> > >>
> > >> Bo
> > >>
> > >>
> > >>
> > >> *Bohdan L. Bodnar*
> > >> Lead Performance Engineer
> > >> 1-312-871-5163 <(312)%20871-5163>
> > >> --
> > >> *E-mail:* *bbod...@us.ibm.com <javascript:;>* <bbod...@us.ibm.com
> <javascript:;>>
> > >> 222 South Riverside Plaza
> > >> Chicago, IL 60606
> > >> United States
> > >>
> > >> [image: Inactive hide details for Stuart Barlow ---03/01/2017
> > >> 10:04:07 AM---Hi. Is there a way to define the duration a test
> > >> should run]Stuart Barlow ---03/01/2017 10:04:07 AM---Hi. Is there a
> > >> way to define the duration a test should run via the command line?
> > >>
> > >> From: Stuart Barlow <stuart.bar...@gmail.com <javascript:;>>
> > >> To: <user@jmeter.apache.org <javascript:;>>
> > >> Date: 03/01/2017 10:04 AM
> > >> Subject: Test Duration
> > >> --
> > >>
> > >>
> > >>
> > >> Hi. Is there a way to define the duration a test should run via the
> > >> command line?
> > >>
> > >> Is there a JMeter property available? Then it could be set using
> > >> the -J command line option
> > >>
> > >> -J[prop_name]=[value]
> > >> defines a local JMeter property.
> > >>
> > >> Sorry if this was asked before.
> > >>
> > >> Thanks
> > >>
> > >> Stuart
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> ---
> > >> -- To unsu
RE: Test Duration
Hi,
You may want to test the "stepping thread group " from jmeter-plugins.
This allows you to setup the duration of each step and much more.
Regards
Sergio Boso
Il 01/Mar/2017 17:48, "Stuart Kenworthy" <stuart.kenwor...@bjss.com> ha
scritto:
> Wow I take that back, it now seems that schedule in v3.1 does seem to do
> what you expect. May want to test properly if using 2.13.
>
> -Original Message-
> From: Stuart Kenworthy [mailto:stuart.kenwor...@bjss.com]
> Sent: 01 March 2017 16:33
> To: JMeter Users List <user@jmeter.apache.org>
> Subject: RE: Test Duration
>
> Does this actually work? In my experience, running a scheduler in command
> line does not work as expected, or at all.
>
> -Original Message-
> From: Antonio Gomes Rodrigues [mailto:ra0...@gmail.com]
> Sent: 01 March 2017 16:30
> To: JMeter Users List <user@jmeter.apache.org>
> Subject: Re: Test Duration
>
> Put ${__P(RUNTIME,100) in the "Thread Group" element in "Duration
> (seconds)" input
>
> And when you run JMeter, use -JRUNTIME=99 in the command line
>
> Instead of 99, put the desired test duration in seconds
>
> 2017-03-01 17:25 GMT+01:00 Stuart Kenworthy <stuart.kenwor...@bjss.com>:
>
> > And how would this be used to control run time within the script itself?
> >
> > -----Original Message-
> > From: sebb [mailto:seb...@gmail.com]
> > Sent: 01 March 2017 16:24
> > To: JMeter Users List <user@jmeter.apache.org>
> > Subject: Re: Test Duration
> >
> > Simpler to use a property reference, for example:
> >
> > ${__P(RUNTIME,100)
> >
> > Then use -JRUNTIME=99 on the command line
> >
> >
> >
> > On 1 March 2017 at 16:18, Antonio Gomes Rodrigues <ra0...@gmail.com>
> > wrote:
> > > Hi,
> > >
> > > Put a JMeter variable in the "Thread Group" element in "Duration
> > (seconds)"
> > > input
> > >
> > > And use -J command line option to define it
> > >
> > > Antonio
> > >
> > > 2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com>:
> > >
> > >> This is exactly the problem that came up in our test organization.
> > >> We couldn't figure it out (running jmeter for a specified time from
> > >> the command line) so, our solution is to have a shell script start
> > >> jmeter and, after the required time, calls shutdown.sh. The whole
> > >> thing works using nohup and works like a charm.
> > >>
> > >> Bo
> > >>
> > >>
> > >>
> > >> *Bohdan L. Bodnar*
> > >> Lead Performance Engineer
> > >> 1-312-871-5163 <(312)%20871-5163>
> > >> --
> > >> *E-mail:* *bbod...@us.ibm.com* <bbod...@us.ibm.com>
> > >> 222 South Riverside Plaza
> > >> Chicago, IL 60606
> > >> United States
> > >>
> > >> [image: Inactive hide details for Stuart Barlow ---03/01/2017
> > >> 10:04:07 AM---Hi. Is there a way to define the duration a test
> > >> should run]Stuart Barlow ---03/01/2017 10:04:07 AM---Hi. Is there a
> > >> way to define the duration a test should run via the command line?
> > >>
> > >> From: Stuart Barlow <stuart.bar...@gmail.com>
> > >> To: <user@jmeter.apache.org>
> > >> Date: 03/01/2017 10:04 AM
> > >> Subject: Test Duration
> > >> --
> > >>
> > >>
> > >>
> > >> Hi. Is there a way to define the duration a test should run via the
> > >> command line?
> > >>
> > >> Is there a JMeter property available? Then it could be set using
> > >> the -J command line option
> > >>
> > >> -J[prop_name]=[value]
> > >> defines a local JMeter property.
> > >>
> > >> Sorry if this was asked before.
> > >>
> > >> Thanks
> > >>
> > >> Stuart
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> ---
> > >> -- To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> > >> For additional commands, e-mail: user-h...@jmeter.apache.org
> > >>
> > >>
> > >>
> > >>
> > >>
> >
> >
RE: Test Duration
Wow I take that back, it now seems that schedule in v3.1 does seem to do what
you expect. May want to test properly if using 2.13.
-Original Message-
From: Stuart Kenworthy [mailto:stuart.kenwor...@bjss.com]
Sent: 01 March 2017 16:33
To: JMeter Users List <user@jmeter.apache.org>
Subject: RE: Test Duration
Does this actually work? In my experience, running a scheduler in command line
does not work as expected, or at all.
-Original Message-
From: Antonio Gomes Rodrigues [mailto:ra0...@gmail.com]
Sent: 01 March 2017 16:30
To: JMeter Users List <user@jmeter.apache.org>
Subject: Re: Test Duration
Put ${__P(RUNTIME,100) in the "Thread Group" element in "Duration (seconds)"
input
And when you run JMeter, use -JRUNTIME=99 in the command line
Instead of 99, put the desired test duration in seconds
2017-03-01 17:25 GMT+01:00 Stuart Kenworthy <stuart.kenwor...@bjss.com>:
> And how would this be used to control run time within the script itself?
>
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 01 March 2017 16:24
> To: JMeter Users List <user@jmeter.apache.org>
> Subject: Re: Test Duration
>
> Simpler to use a property reference, for example:
>
> ${__P(RUNTIME,100)
>
> Then use -JRUNTIME=99 on the command line
>
>
>
> On 1 March 2017 at 16:18, Antonio Gomes Rodrigues <ra0...@gmail.com>
> wrote:
> > Hi,
> >
> > Put a JMeter variable in the "Thread Group" element in "Duration
> (seconds)"
> > input
> >
> > And use -J command line option to define it
> >
> > Antonio
> >
> > 2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com>:
> >
> >> This is exactly the problem that came up in our test organization.
> >> We couldn't figure it out (running jmeter for a specified time from
> >> the command line) so, our solution is to have a shell script start
> >> jmeter and, after the required time, calls shutdown.sh. The whole
> >> thing works using nohup and works like a charm.
> >>
> >> Bo
> >>
> >>
> >>
> >> *Bohdan L. Bodnar*
> >> Lead Performance Engineer
> >> 1-312-871-5163 <(312)%20871-5163>
> >> --
> >> *E-mail:* *bbod...@us.ibm.com* <bbod...@us.ibm.com>
> >> 222 South Riverside Plaza
> >> Chicago, IL 60606
> >> United States
> >>
> >> [image: Inactive hide details for Stuart Barlow ---03/01/2017
> >> 10:04:07 AM---Hi. Is there a way to define the duration a test
> >> should run]Stuart Barlow ---03/01/2017 10:04:07 AM---Hi. Is there a
> >> way to define the duration a test should run via the command line?
> >>
> >> From: Stuart Barlow <stuart.bar...@gmail.com>
> >> To: <user@jmeter.apache.org>
> >> Date: 03/01/2017 10:04 AM
> >> Subject: Test Duration
> >> --
> >>
> >>
> >>
> >> Hi. Is there a way to define the duration a test should run via the
> >> command line?
> >>
> >> Is there a JMeter property available? Then it could be set using
> >> the -J command line option
> >>
> >> -J[prop_name]=[value]
> >> defines a local JMeter property.
> >>
> >> Sorry if this was asked before.
> >>
> >> Thanks
> >>
> >> Stuart
> >>
> >>
> >>
> >>
> >>
> >> ---
> >> -- To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> >> For additional commands, e-mail: user-h...@jmeter.apache.org
> >>
> >>
> >>
> >>
> >>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> For additional commands, e-mail: user-h...@jmeter.apache.org
>
>
> The information included in this email and any files transmitted with
> it may contain information that is confidential and it must not be
> used by, or its contents or attachments copied or disclosed to,
> persons other than the intended addressee. If you have received this
> email in error, please notify BJSS. In the absence of written
> agreement to the contrary BJSS' relevant standard terms of contract
> for any work to be undertaken will apply. Please carry out virus or
> such other checks as you consider appropriate in respect of this
> email. BJSS does not accept responsibility for any adverse effect upon
> your system or data in relation to this email or
RE: Test Duration
Does this actually work? In my experience, running a scheduler in command line
does not work as expected, or at all.
-Original Message-
From: Antonio Gomes Rodrigues [mailto:ra0...@gmail.com]
Sent: 01 March 2017 16:30
To: JMeter Users List <user@jmeter.apache.org>
Subject: Re: Test Duration
Put ${__P(RUNTIME,100) in the "Thread Group" element in "Duration (seconds)"
input
And when you run JMeter, use -JRUNTIME=99 in the command line
Instead of 99, put the desired test duration in seconds
2017-03-01 17:25 GMT+01:00 Stuart Kenworthy <stuart.kenwor...@bjss.com>:
> And how would this be used to control run time within the script itself?
>
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 01 March 2017 16:24
> To: JMeter Users List <user@jmeter.apache.org>
> Subject: Re: Test Duration
>
> Simpler to use a property reference, for example:
>
> ${__P(RUNTIME,100)
>
> Then use -JRUNTIME=99 on the command line
>
>
>
> On 1 March 2017 at 16:18, Antonio Gomes Rodrigues <ra0...@gmail.com>
> wrote:
> > Hi,
> >
> > Put a JMeter variable in the "Thread Group" element in "Duration
> (seconds)"
> > input
> >
> > And use -J command line option to define it
> >
> > Antonio
> >
> > 2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com>:
> >
> >> This is exactly the problem that came up in our test organization.
> >> We couldn't figure it out (running jmeter for a specified time from
> >> the command line) so, our solution is to have a shell script start
> >> jmeter and, after the required time, calls shutdown.sh. The whole
> >> thing works using nohup and works like a charm.
> >>
> >> Bo
> >>
> >>
> >>
> >> *Bohdan L. Bodnar*
> >> Lead Performance Engineer
> >> 1-312-871-5163 <(312)%20871-5163>
> >> --
> >> *E-mail:* *bbod...@us.ibm.com* <bbod...@us.ibm.com>
> >> 222 South Riverside Plaza
> >> Chicago, IL 60606
> >> United States
> >>
> >> [image: Inactive hide details for Stuart Barlow ---03/01/2017
> >> 10:04:07 AM---Hi. Is there a way to define the duration a test
> >> should run]Stuart Barlow ---03/01/2017 10:04:07 AM---Hi. Is there a
> >> way to define the duration a test should run via the command line?
> >>
> >> From: Stuart Barlow <stuart.bar...@gmail.com>
> >> To: <user@jmeter.apache.org>
> >> Date: 03/01/2017 10:04 AM
> >> Subject: Test Duration
> >> --
> >>
> >>
> >>
> >> Hi. Is there a way to define the duration a test should run via the
> >> command line?
> >>
> >> Is there a JMeter property available? Then it could be set using
> >> the -J command line option
> >>
> >> -J[prop_name]=[value]
> >> defines a local JMeter property.
> >>
> >> Sorry if this was asked before.
> >>
> >> Thanks
> >>
> >> Stuart
> >>
> >>
> >>
> >>
> >>
> >> ---
> >> -- To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> >> For additional commands, e-mail: user-h...@jmeter.apache.org
> >>
> >>
> >>
> >>
> >>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> For additional commands, e-mail: user-h...@jmeter.apache.org
>
>
> The information included in this email and any files transmitted with
> it may contain information that is confidential and it must not be
> used by, or its contents or attachments copied or disclosed to,
> persons other than the intended addressee. If you have received this
> email in error, please notify BJSS. In the absence of written
> agreement to the contrary BJSS' relevant standard terms of contract
> for any work to be undertaken will apply. Please carry out virus or
> such other checks as you consider appropriate in respect of this
> email. BJSS does not accept responsibility for any adverse effect upon
> your system or data in relation to this email or any files transmitted
> with it. BJSS Limited, a company registered in England and Wales
> (Company Number 2777575), VAT Registration Number 613295452, Registered
> Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.
>
>
Re: Test Duration
Put ${__P(RUNTIME,100) in the "Thread Group" element in "Duration
(seconds)" input
And when you run JMeter, use -JRUNTIME=99 in the command line
Instead of 99, put the desired test duration in seconds
2017-03-01 17:25 GMT+01:00 Stuart Kenworthy <stuart.kenwor...@bjss.com>:
> And how would this be used to control run time within the script itself?
>
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 01 March 2017 16:24
> To: JMeter Users List <user@jmeter.apache.org>
> Subject: Re: Test Duration
>
> Simpler to use a property reference, for example:
>
> ${__P(RUNTIME,100)
>
> Then use -JRUNTIME=99 on the command line
>
>
>
> On 1 March 2017 at 16:18, Antonio Gomes Rodrigues <ra0...@gmail.com>
> wrote:
> > Hi,
> >
> > Put a JMeter variable in the "Thread Group" element in "Duration
> (seconds)"
> > input
> >
> > And use -J command line option to define it
> >
> > Antonio
> >
> > 2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com>:
> >
> >> This is exactly the problem that came up in our test organization. We
> >> couldn't figure it out (running jmeter for a specified time from the
> >> command line) so, our solution is to have a shell script start jmeter
> >> and, after the required time, calls shutdown.sh. The whole thing
> >> works using nohup and works like a charm.
> >>
> >> Bo
> >>
> >>
> >>
> >> *Bohdan L. Bodnar*
> >> Lead Performance Engineer
> >> 1-312-871-5163 <(312)%20871-5163>
> >> --
> >> *E-mail:* *bbod...@us.ibm.com* <bbod...@us.ibm.com>
> >> 222 South Riverside Plaza
> >> Chicago, IL 60606
> >> United States
> >>
> >> [image: Inactive hide details for Stuart Barlow ---03/01/2017
> >> 10:04:07 AM---Hi. Is there a way to define the duration a test should
> >> run]Stuart Barlow ---03/01/2017 10:04:07 AM---Hi. Is there a way to
> >> define the duration a test should run via the command line?
> >>
> >> From: Stuart Barlow <stuart.bar...@gmail.com>
> >> To: <user@jmeter.apache.org>
> >> Date: 03/01/2017 10:04 AM
> >> Subject: Test Duration
> >> --
> >>
> >>
> >>
> >> Hi. Is there a way to define the duration a test should run via the
> >> command line?
> >>
> >> Is there a JMeter property available? Then it could be set using the
> >> -J command line option
> >>
> >> -J[prop_name]=[value]
> >> defines a local JMeter property.
> >>
> >> Sorry if this was asked before.
> >>
> >> Thanks
> >>
> >> Stuart
> >>
> >>
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> >> For additional commands, e-mail: user-h...@jmeter.apache.org
> >>
> >>
> >>
> >>
> >>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> For additional commands, e-mail: user-h...@jmeter.apache.org
>
>
> The information included in this email and any files transmitted with it
> may contain information that is confidential and it must not be used by, or
> its contents or attachments copied or disclosed to, persons other than the
> intended addressee. If you have received this email in error, please notify
> BJSS. In the absence of written agreement to the contrary BJSS' relevant
> standard terms of contract for any work to be undertaken will apply. Please
> carry out virus or such other checks as you consider appropriate in respect
> of this email. BJSS does not accept responsibility for any adverse effect
> upon your system or data in relation to this email or any files transmitted
> with it. BJSS Limited, a company registered in England and Wales (Company
> Number 2777575), VAT Registration Number 613295452, Registered Office
> Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.
>
> -
> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> For additional commands, e-mail: user-h...@jmeter.apache.org
>
Re: Test Duration
On 1 March 2017 at 16:25, Stuart Kenworthy <stuart.kenwor...@bjss.com> wrote:
> And how would this be used to control run time within the script itself?
[See Antonio's message]
Use it as the Scheduler Duration value.
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: 01 March 2017 16:24
> To: JMeter Users List <user@jmeter.apache.org>
> Subject: Re: Test Duration
>
> Simpler to use a property reference, for example:
>
> ${__P(RUNTIME,100)
>
> Then use -JRUNTIME=99 on the command line
>
>
>
> On 1 March 2017 at 16:18, Antonio Gomes Rodrigues <ra0...@gmail.com> wrote:
>> Hi,
>>
>> Put a JMeter variable in the "Thread Group" element in "Duration (seconds)"
>> input
>>
>> And use -J command line option to define it
>>
>> Antonio
>>
>> 2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com>:
>>
>>> This is exactly the problem that came up in our test organization. We
>>> couldn't figure it out (running jmeter for a specified time from the
>>> command line) so, our solution is to have a shell script start jmeter
>>> and, after the required time, calls shutdown.sh. The whole thing
>>> works using nohup and works like a charm.
>>>
>>> Bo
>>>
>>>
>>>
>>> *Bohdan L. Bodnar*
>>> Lead Performance Engineer
>>> 1-312-871-5163 <(312)%20871-5163>
>>> --
>>> *E-mail:* *bbod...@us.ibm.com* <bbod...@us.ibm.com>
>>> 222 South Riverside Plaza
>>> Chicago, IL 60606
>>> United States
>>>
>>> [image: Inactive hide details for Stuart Barlow ---03/01/2017
>>> 10:04:07 AM---Hi. Is there a way to define the duration a test should
>>> run]Stuart Barlow ---03/01/2017 10:04:07 AM---Hi. Is there a way to
>>> define the duration a test should run via the command line?
>>>
>>> From: Stuart Barlow <stuart.bar...@gmail.com>
>>> To: <user@jmeter.apache.org>
>>> Date: 03/01/2017 10:04 AM
>>> Subject: Test Duration
>>> --
>>>
>>>
>>>
>>> Hi. Is there a way to define the duration a test should run via the
>>> command line?
>>>
>>> Is there a JMeter property available? Then it could be set using the
>>> -J command line option
>>>
>>> -J[prop_name]=[value]
>>> defines a local JMeter property.
>>>
>>> Sorry if this was asked before.
>>>
>>> Thanks
>>>
>>> Stuart
>>>
>>>
>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
>>> For additional commands, e-mail: user-h...@jmeter.apache.org
>>>
>>>
>>>
>>>
>>>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> For additional commands, e-mail: user-h...@jmeter.apache.org
>
>
> The information included in this email and any files transmitted with it may
> contain information that is confidential and it must not be used by, or its
> contents or attachments copied or disclosed to, persons other than the
> intended addressee. If you have received this email in error, please notify
> BJSS. In the absence of written agreement to the contrary BJSS' relevant
> standard terms of contract for any work to be undertaken will apply. Please
> carry out virus or such other checks as you consider appropriate in respect
> of this email. BJSS does not accept responsibility for any adverse effect
> upon your system or data in relation to this email or any files transmitted
> with it. BJSS Limited, a company registered in England and Wales (Company
> Number 2777575), VAT Registration Number 613295452, Registered Office
> Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW.
>
> -
> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
> For additional commands, e-mail: user-h...@jmeter.apache.org
-
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org
RE: Test Duration
And how would this be used to control run time within the script itself?
-Original Message-
From: sebb [mailto:seb...@gmail.com]
Sent: 01 March 2017 16:24
To: JMeter Users List <user@jmeter.apache.org>
Subject: Re: Test Duration
Simpler to use a property reference, for example:
${__P(RUNTIME,100)
Then use -JRUNTIME=99 on the command line
On 1 March 2017 at 16:18, Antonio Gomes Rodrigues <ra0...@gmail.com> wrote:
> Hi,
>
> Put a JMeter variable in the "Thread Group" element in "Duration (seconds)"
> input
>
> And use -J command line option to define it
>
> Antonio
>
> 2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com>:
>
>> This is exactly the problem that came up in our test organization. We
>> couldn't figure it out (running jmeter for a specified time from the
>> command line) so, our solution is to have a shell script start jmeter
>> and, after the required time, calls shutdown.sh. The whole thing
>> works using nohup and works like a charm.
>>
>> Bo
>>
>>
>>
>> *Bohdan L. Bodnar*
>> Lead Performance Engineer
>> 1-312-871-5163 <(312)%20871-5163>
>> --
>> *E-mail:* *bbod...@us.ibm.com* <bbod...@us.ibm.com>
>> 222 South Riverside Plaza
>> Chicago, IL 60606
>> United States
>>
>> [image: Inactive hide details for Stuart Barlow ---03/01/2017
>> 10:04:07 AM---Hi. Is there a way to define the duration a test should
>> run]Stuart Barlow ---03/01/2017 10:04:07 AM---Hi. Is there a way to
>> define the duration a test should run via the command line?
>>
>> From: Stuart Barlow <stuart.bar...@gmail.com>
>> To: <user@jmeter.apache.org>
>> Date: 03/01/2017 10:04 AM
>> Subject: Test Duration
>> --
>>
>>
>>
>> Hi. Is there a way to define the duration a test should run via the
>> command line?
>>
>> Is there a JMeter property available? Then it could be set using the
>> -J command line option
>>
>> -J[prop_name]=[value]
>> defines a local JMeter property.
>>
>> Sorry if this was asked before.
>>
>> Thanks
>>
>> Stuart
>>
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
>> For additional commands, e-mail: user-h...@jmeter.apache.org
>>
>>
>>
>>
>>
-
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org
The information included in this email and any files transmitted with it may
contain information that is confidential and it must not be used by, or its
contents or attachments copied or disclosed to, persons other than the intended
addressee. If you have received this email in error, please notify BJSS. In the
absence of written agreement to the contrary BJSS' relevant standard terms of
contract for any work to be undertaken will apply. Please carry out virus or
such other checks as you consider appropriate in respect of this email. BJSS
does not accept responsibility for any adverse effect upon your system or data
in relation to this email or any files transmitted with it. BJSS Limited, a
company registered in England and Wales (Company Number 2777575), VAT
Registration Number 613295452, Registered Office Address, First Floor, Coronet
House, Queen Street, Leeds, LS1 2TW.
-
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org
Re: Test Duration
Simpler to use a property reference, for example:
${__P(RUNTIME,100)
Then use -JRUNTIME=99 on the command line
On 1 March 2017 at 16:18, Antonio Gomes Rodrigues <ra0...@gmail.com> wrote:
> Hi,
>
> Put a JMeter variable in the "Thread Group" element in "Duration (seconds)"
> input
>
> And use -J command line option to define it
>
> Antonio
>
> 2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com>:
>
>> This is exactly the problem that came up in our test organization. We
>> couldn't figure it out (running jmeter for a specified time from the
>> command line) so, our solution is to have a shell script start jmeter and,
>> after the required time, calls shutdown.sh. The whole thing works using
>> nohup and works like a charm.
>>
>> Bo
>>
>>
>>
>> *Bohdan L. Bodnar*
>> Lead Performance Engineer
>> 1-312-871-5163 <(312)%20871-5163>
>> --
>> *E-mail:* *bbod...@us.ibm.com* <bbod...@us.ibm.com>
>> 222 South Riverside Plaza
>> Chicago, IL 60606
>> United States
>>
>> [image: Inactive hide details for Stuart Barlow ---03/01/2017 10:04:07
>> AM---Hi. Is there a way to define the duration a test should run]Stuart
>> Barlow ---03/01/2017 10:04:07 AM---Hi. Is there a way to define the
>> duration a test should run via the command line?
>>
>> From: Stuart Barlow <stuart.bar...@gmail.com>
>> To: <user@jmeter.apache.org>
>> Date: 03/01/2017 10:04 AM
>> Subject: Test Duration
>> --
>>
>>
>>
>> Hi. Is there a way to define the duration a test should run via the
>> command line?
>>
>> Is there a JMeter property available? Then it could be set using the -J
>> command line option
>>
>> -J[prop_name]=[value]
>> defines a local JMeter property.
>>
>> Sorry if this was asked before.
>>
>> Thanks
>>
>> Stuart
>>
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
>> For additional commands, e-mail: user-h...@jmeter.apache.org
>>
>>
>>
>>
>>
-
To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org
For additional commands, e-mail: user-h...@jmeter.apache.org
Re: Test Duration
Hi, Put a JMeter variable in the "Thread Group" element in "Duration (seconds)" input And use -J command line option to define it Antonio 2017-03-01 17:14 GMT+01:00 Bo Bodnar <bbod...@us.ibm.com>: > This is exactly the problem that came up in our test organization. We > couldn't figure it out (running jmeter for a specified time from the > command line) so, our solution is to have a shell script start jmeter and, > after the required time, calls shutdown.sh. The whole thing works using > nohup and works like a charm. > > Bo > > > > *Bohdan L. Bodnar* > Lead Performance Engineer > 1-312-871-5163 <(312)%20871-5163> > -- > *E-mail:* *bbod...@us.ibm.com* <bbod...@us.ibm.com> > 222 South Riverside Plaza > Chicago, IL 60606 > United States > > [image: Inactive hide details for Stuart Barlow ---03/01/2017 10:04:07 > AM---Hi. Is there a way to define the duration a test should run]Stuart > Barlow ---03/01/2017 10:04:07 AM---Hi. Is there a way to define the > duration a test should run via the command line? > > From: Stuart Barlow <stuart.bar...@gmail.com> > To: <user@jmeter.apache.org> > Date: 03/01/2017 10:04 AM > Subject: Test Duration > -- > > > > Hi. Is there a way to define the duration a test should run via the > command line? > > Is there a JMeter property available? Then it could be set using the -J > command line option > > -J[prop_name]=[value] > defines a local JMeter property. > > Sorry if this was asked before. > > Thanks > > Stuart > > > > > > - > To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org > For additional commands, e-mail: user-h...@jmeter.apache.org > > > > >
Re: Test Duration
This is exactly the problem that came up in our test organization. We couldn't figure it out (running jmeter for a specified time from the command line) so, our solution is to have a shell script start jmeter and, after the required time, calls shutdown.sh. The whole thing works using nohup and works like a charm. Bo Bohdan L. Bodnar Lead Performance Engineer 1-312-871-5163 E-mail: bbod...@us.ibm.com 222 South Riverside Plaza Chicago, IL 60606 United States From: Stuart Barlow <stuart.bar...@gmail.com> To: <user@jmeter.apache.org> Date: 03/01/2017 10:04 AM Subject: Test Duration Hi. Is there a way to define the duration a test should run via the command line? Is there a JMeter property available? Then it could be set using the -J command line option -J[prop_name]=[value] defines a local JMeter property. Sorry if this was asked before. Thanks Stuart - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
Test Duration
Hi. Is there a way to define the duration a test should run via the command line? Is there a JMeter property available? Then it could be set using the -J command line option -J[prop_name]=[value] defines a local JMeter property. Sorry if this was asked before. Thanks Stuart - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
RE: Constant Throughput Timer and test duration conflict
Well, iteration count is only used for debugging or when creating new samplers only. I would gladly share my test plan with you if you want to look at it. I already posted the requirements for the test. This system has over a dozen consumers and exposes over 120 services. So each service must be hit independently which is why a separate thread group is needed for each sampler. This is my first jmeter test plan and I don't doubt that I may be doing something fundamentally wrong. Date: Sat, 10 Mar 2012 22:57:54 -0800 From: a...@apc.kg To: jmeter-u...@jakarta.apache.org Subject: Re: Constant Throughput Timer and test duration conflict If you operate with fixed test duration, then iteration count makes no sense, because the same test duration may include different iterations, depending on server response time. Well, all I hear about your case tells me that there's something may be inefficient in your approach. Maybe you should choose stress-test mode as your primary performance criteria. Just my opinion. - -- Andrey Pohilko JP@GC Maintainer -- View this message in context: http://jmeter.512774.n5.nabble.com/Constant-Throughput-Timer-and-test-duration-conflict-tp5533559p5554206.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
Re: Constant Throughput Timer and test duration conflict
Just to know if my thoughts is on the right way, for this case. If you put a delay after your HTTP Sampler with a dynamic delay timing, considering you could use a post-processor to, say, calculate time spent on the request and set the delay time to (6 - SpentTime). This way you'll have your 1 request per minute requirement. Configure the loop count Test Plan field and *voila*. Other way is using Ramp up to distribute your request in a pre-defined time period between each request (easier to configure IMO). Don't know if it'll be possible, but, IMO, ideas are always welcome. Hope it helps you. Flávio Cysne 2012/3/12 Marcelo Jara marceloj...@hotmail.com Well, iteration count is only used for debugging or when creating new samplers only. I would gladly share my test plan with you if you want to look at it. I already posted the requirements for the test. This system has over a dozen consumers and exposes over 120 services. So each service must be hit independently which is why a separate thread group is needed for each sampler. This is my first jmeter test plan and I don't doubt that I may be doing something fundamentally wrong. Date: Sat, 10 Mar 2012 22:57:54 -0800 From: a...@apc.kg To: jmeter-u...@jakarta.apache.org Subject: Re: Constant Throughput Timer and test duration conflict If you operate with fixed test duration, then iteration count makes no sense, because the same test duration may include different iterations, depending on server response time. Well, all I hear about your case tells me that there's something may be inefficient in your approach. Maybe you should choose stress-test mode as your primary performance criteria. Just my opinion. - -- Andrey Pohilko JP@GC Maintainer -- View this message in context: http://jmeter.512774.n5.nabble.com/Constant-Throughput-Timer-and-test-duration-conflict-tp5533559p5554206.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
Re: Constant Throughput Timer and test duration conflict
Thanks Sebb-2-2, What I gave was just an example. My real tests are much longer ( 1hr). We cannot use a single thread group because we can't let the response time of one sampler affect the throughput of the other. Here are the basic requirements of what I'm being asked to do. 1) Run a test against 120 services which live on one server. These are RESTful web services. Some use xml, some us json. Some requests are GETs, while others are POSTs. 2) Simulate production load and distribution for each of the services. This is very important. We need to keep a steady state of a particular throughput for each service. What I've tried to do is make each sampler independent from each other by putting them in their own thread group. I then put a CTP in each thread group so that I can control the throughput of each service request. The tricky part is determining the number of threads to assign to each thread group, since some samplers may require more threads to achieve the required throughput. Currently the test plan has all the thread groups using a variable for the # of threads. If there is a better way to do this, let me know. I've just started playing around with jmeter a few months ago. An option to shutdown the test when the test duration time is met would help a lot and not affect other test plans. -- View this message in context: http://jmeter.512774.n5.nabble.com/Constant-Throughput-Timer-and-test-duration-conflict-tp5533559p5538131.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
Re: Constant Throughput Timer and test duration conflict
On 3 March 2012 12:17, mjara marceloj...@hotmail.com wrote: I have a test plan with two thread groups. Each thread group has an HTTP sampler and each HTTP sampler has a constant throughput timer (CTP). Each Don't use multiple CTP elements; one per thread should be enough. thread group has 5 threads. If I set the test duration in each thread group to 10 seconds and set CTP to 60 (1 request per second) then the test ends after 10 seconds as expected. 10 seconds is too short for a useful test run. However, if I set the CTP to 1 (1 request per minute) then the test does not end after 10 seconds. It runs for a long time. This is a simplified version of what I'm actually trying to accomplish. My real test plan has 120 thread groups. Each thread group has a different required throughput and some needs many requests per minute and some just need 1. You should probably consider rearranging the test plan to use a single thread group with the appropriate proportions of samplers. I suspect the threads are being delayed to achieve the required throughput, Yes, necessarily. however, I think that when the test is completed based on the test duration value, then all threads should shutdown no matter what state they are in. That does not happen currently. Neither timers nor samplers are interrupted by the expiry of the test duration; this cannot be changed without affecting existing test plans. -- View this message in context: http://jmeter.512774.n5.nabble.com/Constant-Throughput-Timer-and-test-duration-conflict-tp5533559p5533559.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org - To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
