dimitarndimitrov commented on PR #4038: URL: https://github.com/apache/logging-log4j2/pull/4038#issuecomment-3908518423
Thanks for the review, @vy ! Regarding your questions, our use-case is for a relatively new, asynchronous event loop subsystem, which is part of a bigger, pre-existing, Java NIO system that's a node in a distributed system - you can imagine something like an Apache Cassandra node or an Apache Kafka broker. We could see the event loops stuck logging for more than our tolerable window in some rare, but consistently behaving cases, and asynchronous logging seemed like a great fit. After enabling mixed-mode asynchronous logging, we could see a nice little improvement in these cases for the new subsystem, visible in both tail latency figures and CPU flamegraphs. Enabling asynchronous logging for the whole system however would require more validation, especially as in some deployment form factors there are indications that the sole logger thread and maybe more importantly, the sole disruptor ring buffer, might be a bigger issue than what we currently have. -- 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]
