Github user vlsi commented on the issue:
>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" number of samples is 50. Do you remember that the timer is
random. That basically means the number of produced samples for 30 minutes
might be 50, it might be 40, and it might easily be 60. At the end of the day,
poisson arrivals are not guaranteed to produce exactly 50 samples when running
for 30 minutes under 100 samples/hour load.
In practice, everybody wants "round" numbers in the load reports, so "test
duartion" parameter allows the timer to account for the expected test duration.
So, the timer ensures that the number of samples would be exactly 50.
Does that make sense?
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket