You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Philippe Mouawad <ph...@gmail.com> on 2019/02/23 13:43:29 UTC
Improve Thread Group iteration vs scheduler
Hello,
There is apparently a need to improve Thread Group configuration:
-
https://stackoverflow.com/questions/54825237/enable-disable-jmeter-duration-scheduler-based-on-user-command-line-parameters
It's not the first time I see such misunderstanding.
I think we should allow:
- checking scheduler
- AND let 0 in duration mean "Ignore duration and rely on number of
iterations"
This would make the answer above much simpler.
Since empty means 0, it will also avoid an error message, when only number
of iterations is set and scheduler is checked without filling delay nor
duration.
What's your thoughts ?
Regards
--
Philippe Mouawad.
Re: Improve Thread Group iteration vs scheduler
Posted by Philippe Mouawad <ph...@gmail.com>.
Thanks for your answers, indeed I agree with you Paulo
On Mon, Feb 25, 2019 at 10:54 AM Paulo Maia Borges <pm...@temenos.com>
wrote:
> Hi Philippe,
> I completely agree.
>
> I have all my Test Plans configured like that, with variables configuring
> the Thread Groups, and sometimes I want to run a specific length of time,
> other times a specific number of iterations. I, too, have been using
> long-enough "Duration" times.
>
> It would be cleaner to be able to have it set (have a value) but disabled.
> It's also inconsistent because we can «disable» the loop count by setting
> it to -1 but we cannot «disable» the Duration.
>
> I'd say to include (Duration < 0) as «disabled» too, because setting it to
> -1 makes it more consistent with how we disable the Loop Count.
>
> *Actually*, I'm wondering - is there any scenario in which we would want
> to have Duration = 0 be a valid value? I'm thinking Duration = 0 could be
> regarded as a valid setting specifying «do not run», similar to the
> behaviour of LoopCount = 0 and LoopCount = -1. This would make it more
> consistent in behaviour.
>
>
> I think it would make more sense:
> - Duration > 0 : apply duration limit;
> - Duration = 0 : apply duration, means don't run thread group;
> - Duration < 0 : don't apply duration.
>
>
>
>
> Regards,
> Paulo Augusto Maia Borges
> WWVzLCBJJ20gZ2Vla3kuIEJ1dCBzbyBhcmUgeW91IQ==
>
> -----Original Message-----
> From: Philippe Mouawad <ph...@gmail.com>
> Sent: 23 February 2019 13:43
> To: dev@jmeter.apache.org
> Subject: Improve Thread Group iteration vs scheduler
>
> Hello,
>
> There is apparently a need to improve Thread Group configuration:
>
> -
>
> https://stackoverflow.com/questions/54825237/enable-disable-jmeter-duration-scheduler-based-on-user-command-line-parameters
>
>
> It's not the first time I see such misunderstanding.
>
> I think we should allow:
>
> - checking scheduler
> - AND let 0 in duration mean "Ignore duration and rely on number of
> iterations"
>
> This would make the answer above much simpler.
>
> Since empty means 0, it will also avoid an error message, when only number
> of iterations is set and scheduler is checked without filling delay nor
> duration.
>
> What's your thoughts ?
>
> Regards
> --
> Philippe Mouawad.
>
> The information in this e-mail and any attachments is confidential and may
> be legally privileged. It is intended solely for the addressee or
> addressees. Any use or disclosure of the contents of this
> e-mail/attachments by a not intended recipient is unauthorized and may be
> unlawful. If you have received this e-mail in error please notify the
> sender. Please note that any views or opinions presented in this e-mail are
> solely those of the author and do not necessarily represent those of
> TEMENOS. We recommend that you check this e-mail and any attachments
> against viruses. TEMENOS accepts no liability for any damage caused by any
> malicious code or virus transmitted by this e-mail.
>
--
Cordialement.
Philippe Mouawad.
RE: Improve Thread Group iteration vs scheduler
Posted by Paulo Maia Borges <pm...@temenos.com>.
Hi Philippe,
I completely agree.
I have all my Test Plans configured like that, with variables configuring the Thread Groups, and sometimes I want to run a specific length of time, other times a specific number of iterations. I, too, have been using long-enough "Duration" times.
It would be cleaner to be able to have it set (have a value) but disabled. It's also inconsistent because we can «disable» the loop count by setting it to -1 but we cannot «disable» the Duration.
I'd say to include (Duration < 0) as «disabled» too, because setting it to -1 makes it more consistent with how we disable the Loop Count.
*Actually*, I'm wondering - is there any scenario in which we would want to have Duration = 0 be a valid value? I'm thinking Duration = 0 could be regarded as a valid setting specifying «do not run», similar to the behaviour of LoopCount = 0 and LoopCount = -1. This would make it more consistent in behaviour.
I think it would make more sense:
- Duration > 0 : apply duration limit;
- Duration = 0 : apply duration, means don't run thread group;
- Duration < 0 : don't apply duration.
Regards,
Paulo Augusto Maia Borges
WWVzLCBJJ20gZ2Vla3kuIEJ1dCBzbyBhcmUgeW91IQ==
-----Original Message-----
From: Philippe Mouawad <ph...@gmail.com>
Sent: 23 February 2019 13:43
To: dev@jmeter.apache.org
Subject: Improve Thread Group iteration vs scheduler
Hello,
There is apparently a need to improve Thread Group configuration:
-
https://stackoverflow.com/questions/54825237/enable-disable-jmeter-duration-scheduler-based-on-user-command-line-parameters
It's not the first time I see such misunderstanding.
I think we should allow:
- checking scheduler
- AND let 0 in duration mean "Ignore duration and rely on number of
iterations"
This would make the answer above much simpler.
Since empty means 0, it will also avoid an error message, when only number of iterations is set and scheduler is checked without filling delay nor duration.
What's your thoughts ?
Regards
--
Philippe Mouawad.
The information in this e-mail and any attachments is confidential and may be legally privileged. It is intended solely for the addressee or addressees. Any use or disclosure of the contents of this e-mail/attachments by a not intended recipient is unauthorized and may be unlawful. If you have received this e-mail in error please notify the sender. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of TEMENOS. We recommend that you check this e-mail and any attachments against viruses. TEMENOS accepts no liability for any damage caused by any malicious code or virus transmitted by this e-mail.
Re: Improve Thread Group iteration vs scheduler
Posted by Jmeter Tea <jm...@gmail.com>.
Hello
There's existing bug 62100 which in comments decided to make Duration
optional
"I can't see a business case why a delay in threadgroup should mandate a
duration for the threadgroup itself."
https://bz.apache.org/bugzilla/show_bug.cgi?id=62100
On Sat, Feb 23, 2019 at 3:43 PM Philippe Mouawad <ph...@gmail.com>
wrote:
> Hello,
>
> There is apparently a need to improve Thread Group configuration:
>
> -
>
> https://stackoverflow.com/questions/54825237/enable-disable-jmeter-duration-scheduler-based-on-user-command-line-parameters
>
>
> It's not the first time I see such misunderstanding.
>
> I think we should allow:
>
> - checking scheduler
> - AND let 0 in duration mean "Ignore duration and rely on number of
> iterations"
>
> This would make the answer above much simpler.
>
> Since empty means 0, it will also avoid an error message, when only number
> of iterations is set and scheduler is checked without filling delay nor
> duration.
>
> What's your thoughts ?
>
> Regards
> --
> Philippe Mouawad.
>