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 2015/05/17 20:40:50 UTC

Ultimate Thread Group

Hello,
I find And I think I am not the only one that core jmeter lack from the
feature provided by Ultimate Thread Group which is really nice.

I would find it great if this one and Stepping Thread Group could be
contributed to core JMeter .

@Andrei , would this be feasible if a consensus was reached on this ?


Thanks
regards


-- 
Cordialement.
Philippe Mouawad.

Re: Ultimate Thread Group

Posted by Andrey Pokhilko <ap...@ya.ru>.
Since JMeter 2.9 there was no compatibility problems for jp@gc with new
releases of JMeter. I don't see the issue and need to make any automated
check for that. JMeter releases have very detailed changelog and I have
time to test compatibility before JMeter releases.

>From my experience, Ultimate Thread Group is rarely needed. Most of the
times stock Thread Group with proper settings is enough with one
exception of stepping profile.

Andrey Pokhilko

On 05/19/2015 01:48 PM, Philippe Mouawad wrote:
> So I think jmeter-plugins is favored :) as we say "is THE companion".
>
> Regarding tests , I think JP has improved its tests and we try to be
> retro-compatible and document any change for 3rd parties.
> sebb is really keen on maintaining this retro compat ;)
>
> But other automated ideas are welcome.
>
> Regards
>
> On Tuesday, May 19, 2015, Philippe Mouawad <ph...@gmail.com>
> wrote:
>
>> Hi,
>> In 2.13 documentatio was updated:
>>
>> - http://jmeter.apache.org/usermanual/boss.html
>>
>> Regards
>>
>> On Tuesday, May 19, 2015, Vladimir Sitnikov <sitnikov.vladimir@gmail.com
>> <javascript:_e(%7B%7D,'cvml','sitnikov.vladimir@gmail.com');>> wrote:
>>
>>>> We cannot favour one 3rd party plugin over another
>>> We can/should favour all.
>>>
>>> JMeter's front page screams at you with "Highly Extensible core",
>>> while it does not justify the claims.
>>> It would be much better to put references to the relevant sections of
>>> documentations and/or wiki.
>>>
>>> "Highly extensible" claim with zero useful extensions is of no use.
>>> We all know there are good extensions, why don't we list some, so
>>> users could easier get feel of the possibilities?
>>>
>>> Current JMeter wiki does reference lots of external sources:
>>> http://wiki.apache.org/jmeter/
>>>
>>> Here's what I got right from that http://wiki.apache.org/jmeter:
>>> http://wiki.apache.org/jmeter/JMeterMavenPlugin
>>> http://wiki.apache.org/jmeter/MysqlCollectorPlugin
>>> http://wiki.apache.org/jmeter/MonitoringServers
>>> http://wiki.apache.org/jmeter/LogAnalysis
>>> etc.
>>>
>>> In other words, current JMeter's documentation favours some of the
>>> plugins over another.
>>>
>>>
>>>> We don't test and cannot recommend particular 3rd party plugins.
>>> At least Philippe, Andrey, and myself use "jmeter plugins" on a regular
>>> basis.
>>> I have no idea if JMeter release procedure includes integration
>>> testing with jmeter-plugins, but I believe JMeter should at lest
>>> verify that "new JMeter version does not break plugins".
>>> Obviously, JMeter cannot test against all the possible plugins, but it
>>> is a good idea to test for compatibility with well-known plugins.
>>>
>>> I think j-p provides much higher level of quality than "mentioned in
>>> JMeter's documentation
>>> http://wiki.apache.org/jmeter/MysqlCollectorPlugin", so the reference
>>> to j-p in the JMeter's documentation is well deserved.
>>>
>>> Here's what PostgreSQL does in similar case:
>>> 1) The list of "external projects" right in the PostgreSQL core
>>> documentation:
>>> http://www.postgresql.org/docs/9.4/interactive/external-projects.html
>>> "PostgreSQL is a complex software project, and managing the project is
>>> difficult. We have found that many enhancements to PostgreSQL can be
>>> more efficiently developed separately from the core project."
>>>
>>> 2) The list with _lots_ of external plugins/articles right in the
>>> official wiki:
>>> https://wiki.postgresql.org/wiki/Converting_from_other_Databases_to_PostgreSQL
>>> ,  https://wiki.postgresql.org/wiki/Performance_Optimization
>>>
>>> Vladimir
>>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>>


Re: Ultimate Thread Group

Posted by Philippe Mouawad <ph...@gmail.com>.
So I think jmeter-plugins is favored :) as we say "is THE companion".

Regarding tests , I think JP has improved its tests and we try to be
retro-compatible and document any change for 3rd parties.
sebb is really keen on maintaining this retro compat ;)

But other automated ideas are welcome.

Regards

On Tuesday, May 19, 2015, Philippe Mouawad <ph...@gmail.com>
wrote:

> Hi,
> In 2.13 documentatio was updated:
>
> - http://jmeter.apache.org/usermanual/boss.html
>
> Regards
>
> On Tuesday, May 19, 2015, Vladimir Sitnikov <sitnikov.vladimir@gmail.com
> <javascript:_e(%7B%7D,'cvml','sitnikov.vladimir@gmail.com');>> wrote:
>
>> >We cannot favour one 3rd party plugin over another
>>
>> We can/should favour all.
>>
>> JMeter's front page screams at you with "Highly Extensible core",
>> while it does not justify the claims.
>> It would be much better to put references to the relevant sections of
>> documentations and/or wiki.
>>
>> "Highly extensible" claim with zero useful extensions is of no use.
>> We all know there are good extensions, why don't we list some, so
>> users could easier get feel of the possibilities?
>>
>> Current JMeter wiki does reference lots of external sources:
>> http://wiki.apache.org/jmeter/
>>
>> Here's what I got right from that http://wiki.apache.org/jmeter:
>> http://wiki.apache.org/jmeter/JMeterMavenPlugin
>> http://wiki.apache.org/jmeter/MysqlCollectorPlugin
>> http://wiki.apache.org/jmeter/MonitoringServers
>> http://wiki.apache.org/jmeter/LogAnalysis
>> etc.
>>
>> In other words, current JMeter's documentation favours some of the
>> plugins over another.
>>
>>
>> >We don't test and cannot recommend particular 3rd party plugins.
>>
>> At least Philippe, Andrey, and myself use "jmeter plugins" on a regular
>> basis.
>> I have no idea if JMeter release procedure includes integration
>> testing with jmeter-plugins, but I believe JMeter should at lest
>> verify that "new JMeter version does not break plugins".
>> Obviously, JMeter cannot test against all the possible plugins, but it
>> is a good idea to test for compatibility with well-known plugins.
>>
>> I think j-p provides much higher level of quality than "mentioned in
>> JMeter's documentation
>> http://wiki.apache.org/jmeter/MysqlCollectorPlugin", so the reference
>> to j-p in the JMeter's documentation is well deserved.
>>
>> Here's what PostgreSQL does in similar case:
>> 1) The list of "external projects" right in the PostgreSQL core
>> documentation:
>> http://www.postgresql.org/docs/9.4/interactive/external-projects.html
>> "PostgreSQL is a complex software project, and managing the project is
>> difficult. We have found that many enhancements to PostgreSQL can be
>> more efficiently developed separately from the core project."
>>
>> 2) The list with _lots_ of external plugins/articles right in the
>> official wiki:
>> https://wiki.postgresql.org/wiki/Converting_from_other_Databases_to_PostgreSQL
>> ,  https://wiki.postgresql.org/wiki/Performance_Optimization
>>
>> Vladimir
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>

-- 
Cordialement.
Philippe Mouawad.

Re: Ultimate Thread Group

Posted by Philippe Mouawad <ph...@gmail.com>.
Hi,
In 2.13 documentatio was updated:

- http://jmeter.apache.org/usermanual/boss.html

Regards

On Tuesday, May 19, 2015, Vladimir Sitnikov <si...@gmail.com>
wrote:

> >We cannot favour one 3rd party plugin over another
>
> We can/should favour all.
>
> JMeter's front page screams at you with "Highly Extensible core",
> while it does not justify the claims.
> It would be much better to put references to the relevant sections of
> documentations and/or wiki.
>
> "Highly extensible" claim with zero useful extensions is of no use.
> We all know there are good extensions, why don't we list some, so
> users could easier get feel of the possibilities?
>
> Current JMeter wiki does reference lots of external sources:
> http://wiki.apache.org/jmeter/
>
> Here's what I got right from that http://wiki.apache.org/jmeter:
> http://wiki.apache.org/jmeter/JMeterMavenPlugin
> http://wiki.apache.org/jmeter/MysqlCollectorPlugin
> http://wiki.apache.org/jmeter/MonitoringServers
> http://wiki.apache.org/jmeter/LogAnalysis
> etc.
>
> In other words, current JMeter's documentation favours some of the
> plugins over another.
>
>
> >We don't test and cannot recommend particular 3rd party plugins.
>
> At least Philippe, Andrey, and myself use "jmeter plugins" on a regular
> basis.
> I have no idea if JMeter release procedure includes integration
> testing with jmeter-plugins, but I believe JMeter should at lest
> verify that "new JMeter version does not break plugins".
> Obviously, JMeter cannot test against all the possible plugins, but it
> is a good idea to test for compatibility with well-known plugins.
>
> I think j-p provides much higher level of quality than "mentioned in
> JMeter's documentation
> http://wiki.apache.org/jmeter/MysqlCollectorPlugin", so the reference
> to j-p in the JMeter's documentation is well deserved.
>
> Here's what PostgreSQL does in similar case:
> 1) The list of "external projects" right in the PostgreSQL core
> documentation:
> http://www.postgresql.org/docs/9.4/interactive/external-projects.html
> "PostgreSQL is a complex software project, and managing the project is
> difficult. We have found that many enhancements to PostgreSQL can be
> more efficiently developed separately from the core project."
>
> 2) The list with _lots_ of external plugins/articles right in the
> official wiki:
> https://wiki.postgresql.org/wiki/Converting_from_other_Databases_to_PostgreSQL
> ,  https://wiki.postgresql.org/wiki/Performance_Optimization
>
> Vladimir
>


-- 
Cordialement.
Philippe Mouawad.

Re: Ultimate Thread Group

Posted by sebb <se...@gmail.com>.
On 19 May 2015 at 21:44, Philippe Mouawad <ph...@gmail.com> wrote:
> Sebb, I don't share your opinion  and think before anything is changed,
> this needs to be submitted to vote or agreed upon by a certain number of
> commiters.

AFAIK it is ASF policy and therefore not up for discussion.

> Besides , writing "not relevant" to all my arguments is a bit upsetting for
> me , but I will bypass this.

> Anyway, I think this belongs to another thread that would be called for
> example "About 3rd parties mention on JMeter documentation".
>

Agreed.
Sorry, I should have started a new thread.

>
> Back to the initial idea, I still think the 2 UTG and STG should be
> integrated.
> Shmuel seems to agree with my idea.

I think not in the end as he only wanted the duration feature which is
already supported by JMeter.

> Milamber seems to agree with my idea.
> Andrei says it might be complex.
> Vladimir says he does not use this kind of VUs based load tests.
> sebb, I don't know what you think, can you clarify ?

If there is a proven need for the enhancements, then I think we can
consider enhancing JMeter.

However, we will need to ensure that the code is available under the
Apache License.
Also that there are suitable unit tests and supporting documentation.

> Other commiters are welcome to say what they think.
>
> Regards
> Philippe
>
>
> On Tue, May 19, 2015 at 10:33 PM, sebb <se...@gmail.com> wrote:
>
>> On 19 May 2015 at 19:40, Philippe Mouawad <ph...@gmail.com>
>> wrote:
>> > On Tuesday, May 19, 2015, sebb <se...@gmail.com> wrote:
>> >
>> >> On 19 May 2015 at 17:46, Vladimir Sitnikov <sitnikov.vladimir@gmail.com
>> >> <javascript:;>> wrote:
>> >> >>That is very different from promoting specific plugin providers in the
>> >> > JMeter documentation.
>> >> >
>> >> > As Philippe has already pointed out, j-p is already promoted right in
>> >> > the documentation:
>> >> > http://jmeter.apache.org/usermanual/boss.html#jmeter-plugins
>> >>
>> >> I had not noticed that.
>> >>
>> >> I think it is wrong and needs to be removed, along with any other 3rd
>> >> party references.
>> >> However the page can mention the Wiki.
>> >>
>> >> I don't agree with this.
>> > Core jmeter "lacks" today of:
>> > - Excellent reporting (until we implement one bugzilla for it)
>> > - Continuous integration plugin (like maven one)
>> > - Cloud open source ready solution
>>
>> That's not relevant to this issue.
>>
>> >
>> > This page tells users which plugins to use for this in the Open source
>> > field and for now only mentionned some kind of de facto standards.
>>
>> Which is wrong, because there are other plugins.
>> We cannot favour one 3rd party over another.
>>
>> > Besides, All implementors of these plugins are regular contributors of
>> > JMeter and I think they deserve a special mention.
>>
>> Not really relevant.
>>
>> > Furthermore there plugin follow jmeter releases and this is a good thing.
>>
>> Again, not relevant.
>>
>> > Regarding Wiki, today it is highly outdated in terms of content,
>>
>> Go fix it then ...
>>
>> > anybody can write anything meaning content is not really managed and
>> controlled by
>> > us.
>>
>> That's partly the point, because it allows any 3rd party producer to
>> add a link to their product.
>>
>> But we do have control over the content.
>> We can revert bad edits and revoke write access for people who don't play
>> nice.
>>
>> > Finally I find it personaly rather very slow and not sexy at all.
>>
>> Again not relevant.
>>
>> > Felix has build a nice RWD website and I spent some time updating the
>> docs.
>> > All this to say that removing this page would kind of annoy me.
>>
>> I'm sorry about that, but the content can be added to the new
>> JMeterPlugins page I just set up.
>> I should have vetoed the original commit, but I'm afraid I overlooked it.
>>
>> > I think JMeter has a nice community that we need to preserve and make
>> > bigger, wether open source (not only Apache) or even commercial(which is
>> > not against Apache policy from my understanding).
>>
>> Fine, but we still cannot favour some 3rd parties over others.
>>
>> > We are all aware that we have a huge work to do on JMeter and the more we
>> > are the better it is.
>>
>> Again not relevant.
>>
>> > Regards
>> > Philippe
>> >
>> >
>> >> Vladimir
>> >>
>> >
>> >
>> > --
>> > Cordialement.
>> > Philippe Mouawad.
>>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Re: Ultimate Thread Group

Posted by Philippe Mouawad <ph...@gmail.com>.
Sebb, I don't share your opinion  and think before anything is changed,
this needs to be submitted to vote or agreed upon by a certain number of
commiters.
Besides , writing "not relevant" to all my arguments is a bit upsetting for
me , but I will bypass this.

Anyway, I think this belongs to another thread that would be called for
example "About 3rd parties mention on JMeter documentation".


Back to the initial idea, I still think the 2 UTG and STG should be
integrated.
Shmuel seems to agree with my idea.
Milamber seems to agree with my idea.
Andrei says it might be complex.
Vladimir says he does not use this kind of VUs based load tests.
sebb, I don't know what you think, can you clarify ?
Other commiters are welcome to say what they think.

Regards
Philippe


On Tue, May 19, 2015 at 10:33 PM, sebb <se...@gmail.com> wrote:

> On 19 May 2015 at 19:40, Philippe Mouawad <ph...@gmail.com>
> wrote:
> > On Tuesday, May 19, 2015, sebb <se...@gmail.com> wrote:
> >
> >> On 19 May 2015 at 17:46, Vladimir Sitnikov <sitnikov.vladimir@gmail.com
> >> <javascript:;>> wrote:
> >> >>That is very different from promoting specific plugin providers in the
> >> > JMeter documentation.
> >> >
> >> > As Philippe has already pointed out, j-p is already promoted right in
> >> > the documentation:
> >> > http://jmeter.apache.org/usermanual/boss.html#jmeter-plugins
> >>
> >> I had not noticed that.
> >>
> >> I think it is wrong and needs to be removed, along with any other 3rd
> >> party references.
> >> However the page can mention the Wiki.
> >>
> >> I don't agree with this.
> > Core jmeter "lacks" today of:
> > - Excellent reporting (until we implement one bugzilla for it)
> > - Continuous integration plugin (like maven one)
> > - Cloud open source ready solution
>
> That's not relevant to this issue.
>
> >
> > This page tells users which plugins to use for this in the Open source
> > field and for now only mentionned some kind of de facto standards.
>
> Which is wrong, because there are other plugins.
> We cannot favour one 3rd party over another.
>
> > Besides, All implementors of these plugins are regular contributors of
> > JMeter and I think they deserve a special mention.
>
> Not really relevant.
>
> > Furthermore there plugin follow jmeter releases and this is a good thing.
>
> Again, not relevant.
>
> > Regarding Wiki, today it is highly outdated in terms of content,
>
> Go fix it then ...
>
> > anybody can write anything meaning content is not really managed and
> controlled by
> > us.
>
> That's partly the point, because it allows any 3rd party producer to
> add a link to their product.
>
> But we do have control over the content.
> We can revert bad edits and revoke write access for people who don't play
> nice.
>
> > Finally I find it personaly rather very slow and not sexy at all.
>
> Again not relevant.
>
> > Felix has build a nice RWD website and I spent some time updating the
> docs.
> > All this to say that removing this page would kind of annoy me.
>
> I'm sorry about that, but the content can be added to the new
> JMeterPlugins page I just set up.
> I should have vetoed the original commit, but I'm afraid I overlooked it.
>
> > I think JMeter has a nice community that we need to preserve and make
> > bigger, wether open source (not only Apache) or even commercial(which is
> > not against Apache policy from my understanding).
>
> Fine, but we still cannot favour some 3rd parties over others.
>
> > We are all aware that we have a huge work to do on JMeter and the more we
> > are the better it is.
>
> Again not relevant.
>
> > Regards
> > Philippe
> >
> >
> >> Vladimir
> >>
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>



-- 
Cordialement.
Philippe Mouawad.

Re: Ultimate Thread Group

Posted by Vladimir Sitnikov <si...@gmail.com>.
> We cannot favour one 3rd party over another

Any specific reason for that?
Vladimir

Re: Ultimate Thread Group

Posted by sebb <se...@gmail.com>.
On 19 May 2015 at 19:40, Philippe Mouawad <ph...@gmail.com> wrote:
> On Tuesday, May 19, 2015, sebb <se...@gmail.com> wrote:
>
>> On 19 May 2015 at 17:46, Vladimir Sitnikov <sitnikov.vladimir@gmail.com
>> <javascript:;>> wrote:
>> >>That is very different from promoting specific plugin providers in the
>> > JMeter documentation.
>> >
>> > As Philippe has already pointed out, j-p is already promoted right in
>> > the documentation:
>> > http://jmeter.apache.org/usermanual/boss.html#jmeter-plugins
>>
>> I had not noticed that.
>>
>> I think it is wrong and needs to be removed, along with any other 3rd
>> party references.
>> However the page can mention the Wiki.
>>
>> I don't agree with this.
> Core jmeter "lacks" today of:
> - Excellent reporting (until we implement one bugzilla for it)
> - Continuous integration plugin (like maven one)
> - Cloud open source ready solution

That's not relevant to this issue.

>
> This page tells users which plugins to use for this in the Open source
> field and for now only mentionned some kind of de facto standards.

Which is wrong, because there are other plugins.
We cannot favour one 3rd party over another.

> Besides, All implementors of these plugins are regular contributors of
> JMeter and I think they deserve a special mention.

Not really relevant.

> Furthermore there plugin follow jmeter releases and this is a good thing.

Again, not relevant.

> Regarding Wiki, today it is highly outdated in terms of content,

Go fix it then ...

> anybody can write anything meaning content is not really managed and controlled by
> us.

That's partly the point, because it allows any 3rd party producer to
add a link to their product.

But we do have control over the content.
We can revert bad edits and revoke write access for people who don't play nice.

> Finally I find it personaly rather very slow and not sexy at all.

Again not relevant.

> Felix has build a nice RWD website and I spent some time updating the docs.
> All this to say that removing this page would kind of annoy me.

I'm sorry about that, but the content can be added to the new
JMeterPlugins page I just set up.
I should have vetoed the original commit, but I'm afraid I overlooked it.

> I think JMeter has a nice community that we need to preserve and make
> bigger, wether open source (not only Apache) or even commercial(which is
> not against Apache policy from my understanding).

Fine, but we still cannot favour some 3rd parties over others.

> We are all aware that we have a huge work to do on JMeter and the more we
> are the better it is.

Again not relevant.

> Regards
> Philippe
>
>
>> Vladimir
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.

Re: Ultimate Thread Group

Posted by Philippe Mouawad <ph...@gmail.com>.
On Tuesday, May 19, 2015, sebb <se...@gmail.com> wrote:

> On 19 May 2015 at 17:46, Vladimir Sitnikov <sitnikov.vladimir@gmail.com
> <javascript:;>> wrote:
> >>That is very different from promoting specific plugin providers in the
> > JMeter documentation.
> >
> > As Philippe has already pointed out, j-p is already promoted right in
> > the documentation:
> > http://jmeter.apache.org/usermanual/boss.html#jmeter-plugins
>
> I had not noticed that.
>
> I think it is wrong and needs to be removed, along with any other 3rd
> party references.
> However the page can mention the Wiki.
>
> I don't agree with this.
Core jmeter "lacks" today of:
- Excellent reporting (until we implement one bugzilla for it)
- Continuous integration plugin (like maven one)
- Cloud open source ready solution


This page tells users which plugins to use for this in the Open source
field and for now only mentionned some kind of de facto standards.
Besides, All implementors of these plugins are regular contributors of
JMeter and I think they deserve a special mention.
Furthermore there plugin follow jmeter releases and this is a good thing.

Regarding Wiki, today it is highly outdated in terms of content, anybody
can write anything meaning content is not really managed and controlled by
us.
Finally I find it personaly rather very slow and not sexy at all.

Felix has build a nice RWD website and I spent some time updating the docs.
All this to say that removing this page would kind of annoy me.

I think JMeter has a nice community that we need to preserve and make
bigger, wether open source (not only Apache) or even commercial(which is
not against Apache policy from my understanding).

We are all aware that we have a huge work to do on JMeter and the more we
are the better it is.

Regards
Philippe


> Vladimir
>


-- 
Cordialement.
Philippe Mouawad.

Re: Ultimate Thread Group

Posted by sebb <se...@gmail.com>.
On 19 May 2015 at 17:46, Vladimir Sitnikov <si...@gmail.com> wrote:
>>That is very different from promoting specific plugin providers in the
> JMeter documentation.
>
> As Philippe has already pointed out, j-p is already promoted right in
> the documentation:
> http://jmeter.apache.org/usermanual/boss.html#jmeter-plugins

I had not noticed that.

I think it is wrong and needs to be removed, along with any other 3rd
party references.
However the page can mention the Wiki.

> Vladimir

Re: Ultimate Thread Group

Posted by Vladimir Sitnikov <si...@gmail.com>.
>That is very different from promoting specific plugin providers in the
JMeter documentation.

As Philippe has already pointed out, j-p is already promoted right in
the documentation:
http://jmeter.apache.org/usermanual/boss.html#jmeter-plugins

Vladimir

Re: Ultimate Thread Group

Posted by sebb <se...@gmail.com>.
On 19 May 2015 at 10:47, Vladimir Sitnikov <si...@gmail.com> wrote:
>>We cannot favour one 3rd party plugin over another
>
> We can/should favour all.
>
> JMeter's front page screams at you with "Highly Extensible core",
> while it does not justify the claims.
> It would be much better to put references to the relevant sections of
> documentations and/or wiki.
>
> "Highly extensible" claim with zero useful extensions is of no use.
> We all know there are good extensions, why don't we list some, so
> users could easier get feel of the possibilities?
>
> Current JMeter wiki does reference lots of external sources:
> http://wiki.apache.org/jmeter/
>
> Here's what I got right from that http://wiki.apache.org/jmeter:
> http://wiki.apache.org/jmeter/JMeterMavenPlugin
> http://wiki.apache.org/jmeter/MysqlCollectorPlugin
> http://wiki.apache.org/jmeter/MonitoringServers
> http://wiki.apache.org/jmeter/LogAnalysis
> etc.
>
> In other words, current JMeter's documentation favours some of the
> plugins over another.

These pages are created by 3rd parties, not the JMeter project itself.
Anyone who develops a plugin can create a Wiki account and request
editting privileges in order to add links to their favourite plugins.

That is very different from promoting specific plugin providers in the
JMeter documentation.

>
>>We don't test and cannot recommend particular 3rd party plugins.
>
> At least Philippe, Andrey, and myself use "jmeter plugins" on a regular basis.
> I have no idea if JMeter release procedure includes integration
> testing with jmeter-plugins, but I believe JMeter should at lest
> verify that "new JMeter version does not break plugins".
> Obviously, JMeter cannot test against all the possible plugins, but it
> is a good idea to test for compatibility with well-known plugins.

No, I think that is out of scope for the JMeter project.
It is up to the plugin authors to maintain and test their plugins and
to provide user support for them.

> I think j-p provides much higher level of quality than "mentioned in
> JMeter's documentation
> http://wiki.apache.org/jmeter/MysqlCollectorPlugin", so the reference
> to j-p in the JMeter's documentation is well deserved.

That is on the Wiki, not in the JMeter core docs.

> Here's what PostgreSQL does in similar case:
> 1) The list of "external projects" right in the PostgreSQL core
> documentation: http://www.postgresql.org/docs/9.4/interactive/external-projects.html
> "PostgreSQL is a complex software project, and managing the project is
> difficult. We have found that many enhancements to PostgreSQL can be
> more efficiently developed separately from the core project."

That is what the JMeter Wiki is for.

> 2) The list with _lots_ of external plugins/articles right in the
> official wiki: https://wiki.postgresql.org/wiki/Converting_from_other_Databases_to_PostgreSQL
> ,  https://wiki.postgresql.org/wiki/Performance_Optimization

Again, that belongs on the Wiki.

Feel free to re-organise the JMeter Wiki more like the Postgres pages
if you think that would help.

> Vladimir

Re: Ultimate Thread Group

Posted by Vladimir Sitnikov <si...@gmail.com>.
>We cannot favour one 3rd party plugin over another

We can/should favour all.

JMeter's front page screams at you with "Highly Extensible core",
while it does not justify the claims.
It would be much better to put references to the relevant sections of
documentations and/or wiki.

"Highly extensible" claim with zero useful extensions is of no use.
We all know there are good extensions, why don't we list some, so
users could easier get feel of the possibilities?

Current JMeter wiki does reference lots of external sources:
http://wiki.apache.org/jmeter/

Here's what I got right from that http://wiki.apache.org/jmeter:
http://wiki.apache.org/jmeter/JMeterMavenPlugin
http://wiki.apache.org/jmeter/MysqlCollectorPlugin
http://wiki.apache.org/jmeter/MonitoringServers
http://wiki.apache.org/jmeter/LogAnalysis
etc.

In other words, current JMeter's documentation favours some of the
plugins over another.


>We don't test and cannot recommend particular 3rd party plugins.

At least Philippe, Andrey, and myself use "jmeter plugins" on a regular basis.
I have no idea if JMeter release procedure includes integration
testing with jmeter-plugins, but I believe JMeter should at lest
verify that "new JMeter version does not break plugins".
Obviously, JMeter cannot test against all the possible plugins, but it
is a good idea to test for compatibility with well-known plugins.

I think j-p provides much higher level of quality than "mentioned in
JMeter's documentation
http://wiki.apache.org/jmeter/MysqlCollectorPlugin", so the reference
to j-p in the JMeter's documentation is well deserved.

Here's what PostgreSQL does in similar case:
1) The list of "external projects" right in the PostgreSQL core
documentation: http://www.postgresql.org/docs/9.4/interactive/external-projects.html
"PostgreSQL is a complex software project, and managing the project is
difficult. We have found that many enhancements to PostgreSQL can be
more efficiently developed separately from the core project."

2) The list with _lots_ of external plugins/articles right in the
official wiki: https://wiki.postgresql.org/wiki/Converting_from_other_Databases_to_PostgreSQL
,  https://wiki.postgresql.org/wiki/Performance_Optimization

Vladimir

Re: Ultimate Thread Group

Posted by sebb <se...@gmail.com>.
On 18 May 2015 at 20:47, Vladimir Sitnikov <si...@gmail.com> wrote:
> I would rather approach it from "best practices" point of view.
> Even though experienced users might want different kind of workloads,
> I think it makes sense including basic best practices right into the
> documentation.
>
> Well, it would be good if JMeter documentation would suggest "the best
> approach for the test in question".
> I think it is perfectly reasonable to reference "external plugins"
> right in "jmeter core" documentation.
> The message is as follows: we see you might need that case, however we
> did not include it in core because bla-bla-bla, so you can just grab
> that plugin and that will cover your case.

We cannot favour one 3rd party plugin over another, however we can
reiterate that JMeter is open source and plugabble and that there are
external plugins for it.

> How would users find proper plugin if JMeter's site never mentions
> "good and battle-tested" plugins?

We don't test and cannot recommend particular 3rd party plugins.

> For instance, there are two main kinds of load:
> 1) "X requests per second".  This is somewhat covered by
> http://jmeter-plugins.org/wiki/ThroughputShapingTimer/.
> "in-core throughput shaping timer" does not have "good gui to define
> stepping/increasing load".
>
> Both in-core and jmeter-plugins timers canNOT issue "poisson arrival process".
> Here's the description why that is important:
> http://perfdynamics.blogspot.ru/2012/05/load-testing-with-uniform-vs.html
>
> 2) "X concurrent threads working non-stop".
> Frankly speaking, I never use that kind of tests, however I might
> agree they might serve their purpose.
> This is covered by Ultimate Thread Group.
>
> Vladimir

Re: Ultimate Thread Group

Posted by Vladimir Sitnikov <si...@gmail.com>.
I would rather approach it from "best practices" point of view.
Even though experienced users might want different kind of workloads,
I think it makes sense including basic best practices right into the
documentation.

Well, it would be good if JMeter documentation would suggest "the best
approach for the test in question".
I think it is perfectly reasonable to reference "external plugins"
right in "jmeter core" documentation.
The message is as follows: we see you might need that case, however we
did not include it in core because bla-bla-bla, so you can just grab
that plugin and that will cover your case.

How would users find proper plugin if JMeter's site never mentions
"good and battle-tested" plugins?

For instance, there are two main kinds of load:
1) "X requests per second".  This is somewhat covered by
http://jmeter-plugins.org/wiki/ThroughputShapingTimer/.
"in-core throughput shaping timer" does not have "good gui to define
stepping/increasing load".

Both in-core and jmeter-plugins timers canNOT issue "poisson arrival process".
Here's the description why that is important:
http://perfdynamics.blogspot.ru/2012/05/load-testing-with-uniform-vs.html

2) "X concurrent threads working non-stop".
Frankly speaking, I never use that kind of tests, however I might
agree they might serve their purpose.
This is covered by Ultimate Thread Group.

Vladimir

Re: Ultimate Thread Group

Posted by Shmuel Krakower <sh...@gmail.com>.
www.beatsoo.org - free application performance monitoring from world wide
locations.

On May 18, 2015 10:56 PM, "Vladimir Sitnikov" <si...@gmail.com>
wrote:
>
> > The scheduler use absolute times and doesn't serve
> well this need.
>
> Clear "start time" and "end time" fields (make them empty)
> Put the required test duration into "duration" field (in seconds as
> the label suggests) of a thread group.
> That is it.

Good point.
>
> >I can't imagine building complex scenarios without the thread groups
coming
> >from the jmeter plugins project.
>
> Please go ahead and tell us which requirements force you to use thread
> groups from jmeter-plugins.
> We (at my company) do have complex tests, complex loads, etc, yet we
> use out-of-the-box thread groups.
>

Actually only the one mentioned above which is obsolete.

I was using the ramp down feature for quite some time but I don't anymore.
So no other points from me.

> Vladimir

Re: Ultimate Thread Group

Posted by Vladimir Sitnikov <si...@gmail.com>.
> The scheduler use absolute times and doesn't serve
well this need.

Clear "start time" and "end time" fields (make them empty)
Put the required test duration into "duration" field (in seconds as
the label suggests) of a thread group.
That is it.

>I can't imagine building complex scenarios without the thread groups coming
>from the jmeter plugins project.

Please go ahead and tell us which requirements force you to use thread
groups from jmeter-plugins.
We (at my company) do have complex tests, complex loads, etc, yet we
use out-of-the-box thread groups.

Vladimir

Re: Ultimate Thread Group

Posted by Shmuel Krakower <sh...@gmail.com>.
Hi sebb
The most important part of the ultimate thread group for me is that it
allows me to predefine for how long a test should run.
I.e. what would be the way today to configure a test to run for
specifically two hours? The scheduler use absolute times and doesn't serve
well this need.

I can't imagine building complex scenarios without the thread groups coming
from the jmeter plugins project.

If others feel the same way too, I guess it make it a valid feature to have
in the JMeter core.

On the other hand, I'm fine with using it from the plugins project as I do
today...

www.beatsoo.org - free application performance monitoring from world wide
locations.
On May 18, 2015 9:33 PM, "Milamber" <mi...@apache.org> wrote:

>
> I'm agree with Philippe, particularly for the Stepping Thread Group.
> That would be a great addition for JMeter core, and allow the newbies to
> start quickly some load test with level of charge.
>
> On 18/05/2015 19:10, Philippe Mouawad wrote:
>
>> Hi sebb,
>> Mainly an easy and user friendly way to create a simple to complex
>> injection profile with a visual representation of it.
>> Nearly all open source and commercial tools have it.
>> We use it a lot at our company and frankly I believe it's a big lack in
>> core jmeter.
>>
>> Have a lookt at this thesis comparing tools and see the page 30:
>> -
>> http://is.muni.cz/th/256206/fi_m/dp.pdf
>>
>> And it is always a question I get when I give trainings or explain JMeter.
>>
>> So if Andrei would be ok for an integration I think it is worth having it.
>>
>> Regards
>>
>> On Monday, May 18, 2015, sebb <se...@gmail.com> wrote:
>>
>>  On 17 May 2015 at 19:40, Philippe Mouawad <philippe.mouawad@gmail.com
>>> <javascript:;>> wrote:
>>>
>>>> Hello,
>>>> I find And I think I am not the only one that core jmeter lack from the
>>>> feature provided by Ultimate Thread Group which is really nice.
>>>>
>>> What feature(s) does this provide that you think are lacking?
>>>
>>>  I would find it great if this one and Stepping Thread Group could be
>>>> contributed to core JMeter .
>>>>
>>>> @Andrei , would this be feasible if a consensus was reached on this ?
>>>>
>>>>
>>>> Thanks
>>>> regards
>>>>
>>>>
>>>> --
>>>> Cordialement.
>>>> Philippe Mouawad.
>>>>
>>>
>>
>

Re: Ultimate Thread Group

Posted by Milamber <mi...@apache.org>.
I'm agree with Philippe, particularly for the Stepping Thread Group.
That would be a great addition for JMeter core, and allow the newbies to 
start quickly some load test with level of charge.

On 18/05/2015 19:10, Philippe Mouawad wrote:
> Hi sebb,
> Mainly an easy and user friendly way to create a simple to complex
> injection profile with a visual representation of it.
> Nearly all open source and commercial tools have it.
> We use it a lot at our company and frankly I believe it's a big lack in
> core jmeter.
>
> Have a lookt at this thesis comparing tools and see the page 30:
> -
> http://is.muni.cz/th/256206/fi_m/dp.pdf
>
> And it is always a question I get when I give trainings or explain JMeter.
>
> So if Andrei would be ok for an integration I think it is worth having it.
>
> Regards
>
> On Monday, May 18, 2015, sebb <se...@gmail.com> wrote:
>
>> On 17 May 2015 at 19:40, Philippe Mouawad <philippe.mouawad@gmail.com
>> <javascript:;>> wrote:
>>> Hello,
>>> I find And I think I am not the only one that core jmeter lack from the
>>> feature provided by Ultimate Thread Group which is really nice.
>> What feature(s) does this provide that you think are lacking?
>>
>>> I would find it great if this one and Stepping Thread Group could be
>>> contributed to core JMeter .
>>>
>>> @Andrei , would this be feasible if a consensus was reached on this ?
>>>
>>>
>>> Thanks
>>> regards
>>>
>>>
>>> --
>>> Cordialement.
>>> Philippe Mouawad.
>


Re: Ultimate Thread Group

Posted by Philippe Mouawad <ph...@gmail.com>.
Hi sebb,
Mainly an easy and user friendly way to create a simple to complex
injection profile with a visual representation of it.
Nearly all open source and commercial tools have it.
We use it a lot at our company and frankly I believe it's a big lack in
core jmeter.

Have a lookt at this thesis comparing tools and see the page 30:
-
http://is.muni.cz/th/256206/fi_m/dp.pdf

And it is always a question I get when I give trainings or explain JMeter.

So if Andrei would be ok for an integration I think it is worth having it.

Regards

On Monday, May 18, 2015, sebb <se...@gmail.com> wrote:

> On 17 May 2015 at 19:40, Philippe Mouawad <philippe.mouawad@gmail.com
> <javascript:;>> wrote:
> > Hello,
> > I find And I think I am not the only one that core jmeter lack from the
> > feature provided by Ultimate Thread Group which is really nice.
>
> What feature(s) does this provide that you think are lacking?
>
> > I would find it great if this one and Stepping Thread Group could be
> > contributed to core JMeter .
> >
> > @Andrei , would this be feasible if a consensus was reached on this ?
> >
> >
> > Thanks
> > regards
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>


-- 
Cordialement.
Philippe Mouawad.

Re: Ultimate Thread Group

Posted by sebb <se...@gmail.com>.
On 17 May 2015 at 19:40, Philippe Mouawad <ph...@gmail.com> wrote:
> Hello,
> I find And I think I am not the only one that core jmeter lack from the
> feature provided by Ultimate Thread Group which is really nice.

What feature(s) does this provide that you think are lacking?

> I would find it great if this one and Stepping Thread Group could be
> contributed to core JMeter .
>
> @Andrei , would this be feasible if a consensus was reached on this ?
>
>
> Thanks
> regards
>
>
> --
> Cordialement.
> Philippe Mouawad.

Re: Ultimate Thread Group

Posted by sebb <se...@gmail.com>.
On 18 May 2015 at 15:20, Andrey Pokhilko <ap...@ya.ru> wrote:
> Hi,
>
> Maybe just providing couple of links from documentation might help users
> to find the plugin quickly, without needing to merge complex code (it
> needs charting classes for preview etc).

We cannot favour one particular 3rd party plugin provider over
another, especially in the docs that are included with JMeter.

The JMeter Wiki has some sections for 3rd party resources.

> Andrey Pokhilko
>
> On 05/17/2015 09:40 PM, Philippe Mouawad wrote:
>> Hello,
>> I find And I think I am not the only one that core jmeter lack from the
>> feature provided by Ultimate Thread Group which is really nice.
>>
>> I would find it great if this one and Stepping Thread Group could be
>> contributed to core JMeter .
>>
>> @Andrei , would this be feasible if a consensus was reached on this ?
>>
>>
>> Thanks
>> regards
>>
>>
>

Re: Ultimate Thread Group

Posted by Andrey Pokhilko <ap...@ya.ru>.
Hi,

Maybe just providing couple of links from documentation might help users
to find the plugin quickly, without needing to merge complex code (it
needs charting classes for preview etc).

Andrey Pokhilko

On 05/17/2015 09:40 PM, Philippe Mouawad wrote:
> Hello,
> I find And I think I am not the only one that core jmeter lack from the
> feature provided by Ultimate Thread Group which is really nice.
>
> I would find it great if this one and Stepping Thread Group could be
> contributed to core JMeter .
>
> @Andrei , would this be feasible if a consensus was reached on this ?
>
>
> Thanks
> regards
>
>