onionzz commented on issue #6278: URL: https://github.com/apache/jmeter/issues/6278#issuecomment-2121654474
> After looking a bit deeper here, I think the resolution of milliseconds for the calculated delay is not enough, when we are trying a high throughput rate with a low thread count. For example, if we set 30,000 or 40,000 requests as a target with one thread and use active thread as the mode. Then the calculation for the two request/s targets would be: > > 30,000 => 60,000/30,000 = 2 => rounded to 2 40,000 => 60,000/40,000 = 1.5 => rounded to 2 > > It doesn't change, when we calculate the same with microseconds instead and still round at the end, as it would be: > > 30,000 => 60,000,000/30,000 = 2,000 => round to milliseconds => 2 40,000 => 60,000,000/40,000 = 1,500 => round to milliseconds => 2 > > Apart from this, it is probably still a good idea to change the resolution. Use microseconds may be quite different when `Math.max(now, nextRequestTime)`, and then the result of this will produce an effect on the delay. But calcuate with microseconds will still have the problem when the throughput rate is high enough. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
