https://bz.apache.org/bugzilla/show_bug.cgi?id=65031
Felix Schumacher <felix.schumac...@internetallee.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #2 from Felix Schumacher <felix.schumac...@internetallee.de> ---
The main problem here, is that the delay is not added to the first thread. If
we would change this, I think it would add up all nicely.
The reasoning was probably, that the test should start right away instead of
waiting some time (The user pressed start, why didn't it start?).
I think, we have three possible ways to solve this:
1) do nothing (nobody else seems to care ;) )
2) start with a delay and everything should be fine (apart from those, that
expect an instant start)
That is delayPerThread = rampUp / nr_of_threads and start time = now +
thread_nr * delayPerThread (thread_nr starting from 1!)
3) start right away and calculate the differences between the threads by
subtracting one from the number of threads.
That is delayPerThread = rampup / max(nr_of_threads - 1, 1) and start time =
now + thread_nr * delayPerThread (thread_nr starting from 0!)
I tend to changing the behaviour to variant three (longer delayPerThread and
instant start)
@all what do you think?
--
You are receiving this mail because:
You are the assignee for the bug.
