vlsi commented on pull request #602: URL: https://github.com/apache/jmeter/pull/602#issuecomment-650598550
> is always in our tests when the storage becomes full Well, technically speaking, you produce too many samples and the writer can't cope with them. It does not look like ABQ/Disruptor/JCTools can magically make the writer faster. Can you please clarify the hardware you used for the test? I see you are launching 3000 threads non-stop. What is the number of CPUs you have? --- As we can't make the "result saver" / "result processor" infinitely fast, we might want to allow to use multiple threads for result processing. WDYT? ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
