Github user a-sure commented on the issue:
https://github.com/apache/jmeter/pull/231
@vlsi,
since thread departure schedule is pre-generated for defined timeframe,
what about adding ability to log this schedule into file ?
Another interesting feature would be to have real depar
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
@pmouawad , please review https://github.com/apache/jmeter/pull/369
---
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/231
Hi @vsi,
When do you think youâll be able to provide a documentation PR ?
Thanks
---
Github user ham1 commented on the issue:
https://github.com/apache/jmeter/pull/231
Is there a better name which makes the difference between the Constant
Throughput Timer clearer, or should that be deprecated or just replaced with
this?
---
Github user ra0077 commented on the issue:
https://github.com/apache/jmeter/pull/231
Hi,
Thank to your (Vlad and Philippe) for your works
I don't think to put Poisson it's a good idea because if user don't know
poisson law, he will not understant the goal of this
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
"Precise Throughput Timer" sounds goods.
PS. There's "Poisson Random Timer" in JMeter:
http://jmeter.apache.org/usermanual/component_reference.html#Poisson_Random_Timer
I guess it is used much
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/231
@vlsi ,
What about:
- Poisson Arrivals timer ?
- Precise Throughput Timer ?
---
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
@pmouawad , just a quick note: I do not like "exponential" name very much.
It is scientific, however it has 0.01% probability to be well-understood by
regular engineers. What do you think regarding the
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/231
Hi @vsi,
It looks ok to me, if you can add doc as separate PR it would be great !
Thanks
---
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
@pmouawad , thanks anyway for giving it a spin.
Do you think it requires changes?
If not, I think I can prepare a doc draft.
---
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
> Philippe: It is just that as per your confirmation, one of the aims of
this new component was:
> Vladimir: "The very basic requirement is to ensure you end up exactly 50
iterations **per hour**.
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/231
Hi @vlsi ,
Thanks for your clarifications.
It is just that as per your confirmation, one of the aims of this new
component was:
**"The very basic requirement is to ensure you end up exact
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
>Is it really supposed to be exact ?
Let me ask another question: "is thread scheduler=120sec supposed to make
the test to last exactly 120 seconds"?
Note: **timers do not limit the num
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/231
Hi @vlsi ,
Thanks for your feedback.
I tried many configurations including thread delay to 0, and I never really
reach exact sampling on duration.
Is it really supposed to be exact ?
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
>AS you can see I don't get exact executions:
@pmouawad , that's a good question.
The timer uses `testStarted` (see
https://github.com/apache/jmeter/pull/231/files#diff-e5e4a43d21590a05
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/231
Hi @vlsi ,
I tried the component and if I have this:
https://user-images.githubusercontent.com/3127467/34276777-3096e68e-e6a3-11e7-9726-759d086d11d2.png";>
https://user-images.githubuserco
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
>Could you confirm your component implements the following features:
That's true.
---
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/231
Hi @vlsi ,
Could you confirm your component implements the following features:
1) "Specific number of iterations per hour".
The very basic requirement is to ensure you end up exactly 50
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
>I will commit this PR unless there is a NO GO within 2 days.
Philippe, thanks for looking into this. I'm afraid the documentation is
missing.
---
Hi,
No problem for me and very happy to have this PR merged in JMeter
Antonio
2017-11-02 21:34 GMT+01:00 Philippe Mouawad :
> Hi Antonio,
> For the doc I can do it.
> For the more intuitive GUI, can't we improve it later ?
> Regards
>
> On Thu, Nov 2, 2017 at 9:23 PM, Antonio Gomes Rodrigues
>
Hi Antonio,
For the doc I can do it.
For the more intuitive GUI, can't we improve it later ?
Regards
On Thu, Nov 2, 2017 at 9:23 PM, Antonio Gomes Rodrigues
wrote:
> Hi,
>
> I think we need more doc and maybe a more intuitive GUI
>
> Antonio
>
>
>
> 2017-11-02 21:13 GMT+01:00 pmouawad :
>
> > Gi
Hi,
I think we need more doc and maybe a more intuitive GUI
Antonio
2017-11-02 21:13 GMT+01:00 pmouawad :
> Github user pmouawad commented on the issue:
>
> https://github.com/apache/jmeter/pull/231
>
> Hello,
> I will commit this PR unless there is a NO GO within 2 days.
>
>
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/231
Hello,
I will commit this PR unless there is a NO GO within 2 days.
Thanks
---
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
>In my test plan I have 3 http request and one Exponential Timer at the
same level
That does not work like this.
Please wrap "expenential timer" into some sampler (e.g. debug action or
what
Github user ra0077 commented on the issue:
https://github.com/apache/jmeter/pull/231
Hi,
In my test plan I have 3 http request and one Exponential Timer at the same
level
When I run my script, only first http request are executed whereas with
"Constant Throughput Tim
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
>I have some strange behavior in some test
What is the behavior?
Don't get me wrong, but I think the UI should be obvious. If the UI is
obscure and/or the tooltip does not help, then it
Github user ra0077 commented on the issue:
https://github.com/apache/jmeter/pull/231
Yes I have read it but I have some strange behavior in some test
It's why I would like to know how do you use it
Antonio
---
If your project is set up for it, you can reply to this email
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
@ra0077 , have you seen the tooltips for the input values of the timer?
I'm sure those should explain all the things.
---
If your project is set up for it, you can reply to this email and have
Github user ra0077 commented on the issue:
https://github.com/apache/jmeter/pull/231
Hi Vladimir,
No idea for the UI
Anybody have the answer?
To help me to understand how to use it, can you provide me some JMeter jmx
file for each goal ("Specific number of it
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
> Too much parameter
Well, UI is built by JMeter OOB:
https://github.com/apache/jmeter/pull/231/files#diff-fc396f633dbdaf0a98c5472613e9190dR25
Do you know if BeanInfoSupport can create
Github user ra0077 commented on the issue:
https://github.com/apache/jmeter/pull/231
Hi,
My opinion is that the GUI is too complex because :
Too much parameter
You try to make too much different things in it
And these things
1) "Specific number of ite
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
> And if "test duration" parameter is not equal to expected test duration?
Nothing breaks. The idea is as follows: each "test duration" the timer
produces exact number of samples.
For i
Github user ra0077 commented on the issue:
https://github.com/apache/jmeter/pull/231
Thank to the quick answer
"so "test duration" parameter allows the timer to account for the expected
test duration."
And if "test duration" parameter is not equal to expected test dur
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
>I don't understand how to use "Test duration" parameter
The timer is random. Suppose one wants to have "100 samples per hour".
Suppose the test duration is 30 minutes.
The "expected
Github user ra0077 commented on the issue:
https://github.com/apache/jmeter/pull/231
Hi,
Thanks for the patch too.
I don't understand how to use "Test duration" parameter
Thank
Antonio
---
If your project is set up for it, you can reply to this email and have your
Github user vlsi commented on the issue:
https://github.com/apache/jmeter/pull/231
> Any reason for not using ThreadLocalRandom.current() instead of Random ?
TLR does not support setSeed. setSeed is required to get reproducible
workloads.
>
https://docs.oracle.com/ja
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/231
Hello,
Thanks for the patch.
First review look good to me.
Any reason for not using ThreadLocalRandom.current() instead of Random ?
Regards
Philippe
---
If your project is s
37 matches
Mail list logo