mattrpav opened a new issue, #2275: URL: https://github.com/apache/activemq/issues/2275
While performing benchmarks against 6.3.0 with virtual threads, I observed an unexpected degradation in parallelized throughput. I honed the test down to everything stripped back and found that since memoryUsage is shared across all destinations the locking here accounted for the majority of wait time. Moving to a lock-free data structure for this metric removes the bottleneck. LongAdder does use more memory than an AtomicLong (up to ~2KB), but makes sense in this use case. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
