Re: [apache/jmeter] This implements "Provide ability to configure whether a new iteration is a new user or same user" (BUG 62861) (#470)

[Philippe Mouawad <p....@ubik-ingenierie.com>]

On Sunday, June 23, 2019, Vladimir Sitnikov <no...@github.com>
wrote:

> Do you propose to move setIsSameUser/isSameUser into AbstractThreadGroup ?
>
> As for me, "new iteration is a new user / same user" does not belong to a
> Thread. It belongs to whatever is controlling the iterations. And it turns
> out JMeterThread is reusing loop parameters, so it looks like "reset user"
> should be there.
>

I don’ share your opinion :
Loop Controller is more of an algorithmic element and has no notion of user.
Thread Group control user behaviour:
- how many
- how they ramp up
- how much they run

And now we’re adding what kind are they.
Another new element makes it maybe more flexible but more complex.



What if we would like to add "relogin user after each 15 min" and so on?
>
how would it be impacted by this feature?
- can you illustrate how you would do it now and how this feature impacts
it ?


>
> That would bloat JMeterThread with irrelevant features, especially when
> load protocol has no notion of "user".
> For instance, if JMeter is used to drive TCP load, then "new iteration is
> a new user" would be obscure.
>




so it would just be ignored

> Could the same behavior be configured by adding a listener/configuration
> element?
>
>
> If that is possible, why don't we go with that approach?
>

Feel free to propose a PR illustrating it or amending this one.



> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/jmeter/pull/470?email_source=notifications&email_token=ADSIZY64UKLL4WQGL3WQZALP34XIZA5CNFSM4HZD5EFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYKZI5I#issuecomment-504730741>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ADSIZYY6BBG3226KRLS3HN3P34XIZANCNFSM4HZD5EFA>
> .
>


-- 


[image: logo Ubik Ingenierie] <https://www.ubik-ingenierie.com> Philippe
Mouawad
Senior Performance Expert
320914981 <+33320914981> | p.mouawad@ubik-ingenierie.com
[image: ubik-ingenierie.com] ubik-ingenierie.com
<https://www.ubik-ingenierie.com> | [image: 03.20.91.49.81] 03.20.91.49.81
<+33320914981> | [image: 23 rue du chemin de fer , 59100 , Roubaix] 23 rue
du chemin de fer, 59100, Roubaix
<https://www.openstreetmap.org/#map=18/50.69454/3.16455>

Re: [apache/jmeter] This implements "Provide ability to configure whether a new iteration is a new user or same user" (BUG 62861) (#470)

[Philippe Mouawad <ph...@gmail.com>]

On Sunday, June 23, 2019, Vladimir Sitnikov <si...@gmail.com>
wrote:

> Just a side note: how the proposed feature differs from existing property
> "httpclient.reset_state_on_thread_group_iteration=true" ?


if you look at initial bugzilla, you’ll see it’s related and provides
ability to have the same Jmeter instance works in both mode by configuring
it at thread group level.
The initial property could now even be removed

>
> Can you please clarify how the proposed feature differs from existing
> "clear auth on each iteration" checkbox?
> https://jmeter.apache.org/usermanual/component_reference.html#HTTP_
> Authorization_Manager


First, I notice the PR should include also this component in the user
(new/returning) configuration, thanks for indirectly pinpointing it.
I’ll update PR

The idea of PR is to simplify configuration by :

- making cookiemanager use the configuration at thread leven
- same for cachemanager
- same for Auth Manager

In the end, the 3 components will be by default configured to rely on
Thread Group config
and HTtp request will be able to use it also.
Which is not possible currently.


> It looks like JMeter has at least two related features, and you propose to
> add one more.
> If the added feature is indeed different from all of the above, would you
> please add relevant documentation that would explain the difference and the
> suggested use cases?


It is expected soon


>
> Vladimir>What if we would like to add "relogin user after each 15 min" and
> so on?
>
> Philippe>how would it be impacted by this feature?
> Philippe>- can you illustrate how you would do it now and how this feature
> impacts
> it ?
>
> 1) It will be very complicated in the UI, and "thread" does not look the
> proper abstraction point.


How does this feature make it more complex?
This feature makes possible what was not and does not limit any existing
feature.
Such feature is available in alternative tools (commercial)


> 2) It is not clear how the proposed change would play with custom thread
> groups (e.g. from JMeterPlugins)


Until their code is updated, they’ll work as today.


>
> Vladimir
>


-- 
Cordialement.
Philippe Mouawad.

Re: [apache/jmeter] This implements "Provide ability to configure whether a new iteration is a new user or same user" (BUG 62861) (#470)

[Vladimir Sitnikov <si...@gmail.com>]

Just a side note: how the proposed feature differs from existing property
"httpclient.reset_state_on_thread_group_iteration=true" ?

Can you please clarify how the proposed feature differs from existing
"clear auth on each iteration" checkbox?
https://jmeter.apache.org/usermanual/component_reference.html#HTTP_Authorization_Manager

It looks like JMeter has at least two related features, and you propose to
add one more.
If the added feature is indeed different from all of the above, would you
please add relevant documentation that would explain the difference and the
suggested use cases?

Vladimir>What if we would like to add "relogin user after each 15 min" and
so on?

Philippe>how would it be impacted by this feature?
Philippe>- can you illustrate how you would do it now and how this feature
impacts
it ?

1) It will be very complicated in the UI, and "thread" does not look the
proper abstraction point.
2) It is not clear how the proposed change would play with custom thread
groups (e.g. from JMeterPlugins)

Vladimir