vlsi opened a new issue, #5943: URL: https://github.com/apache/jmeter/issues/5943
### Expected behavior JMeter should support cases when the test produces many threads. It should probably discard "Thread started", and "Thread is done" messages when the thread startup rate exceeds a certain threshold. ### Actual behavior JMeter executes ~5-10K requests per second only, and it spends significant time on logging "Thread started" and "Thread is done" messages (they synchronize on the logger, and they cause logging pane updates in the UI). A workaround is to adjust the `org.apache.jmeter.threads.JMeterThread` logging category to `warning` level. ### Steps to reproduce the problem Create Open Model Thread Group with debug sampler. Use `rate(100000/sec) random_arrivals(60 sec)` for the schedule ### JMeter Version 5.5 ### Java Version _No response_ ### OS Version _No response_ -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
