[GitHub] [jmeter] vlsi commented on issue #5943: Thread started/finished logging incur significant overhead when executing many JMeter threads

["vlsi (via GitHub)" <gi...@apache.org>]

vlsi commented on issue #5943:
URL: https://github.com/apache/jmeter/issues/5943#issuecomment-1563103289

   OpenModelTG already uses a thread pool, so it does not create/destroy hardware threads.
   
   Currently OMTG creates JMeterThreads in a single thread, and it reaches 160'000 samples per second. It might be a better idea to reuse the cloned plans.
   
   Currently we have a significant memory overhead caused by test elements cloning, so I am not sure virtual threads would change much. We can try them (e.g. call with reflection), however, I am not sure it will yield much for the current JMeter design


-- 
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-unsubscribe@jmeter.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org