will-zdu closed issue #3635: High CPU usage in async mode with Log4j2
URL: https://github.com/apache/logging-log4j2/issues/3635
--
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.
ppkarwasz commented on issue #3635:
URL:
https://github.com/apache/logging-log4j2/issues/3635#issuecomment-2837716456
> I know this configuration can avoid this problem, but the question is
whether there is a problem with this default configuration and whether it needs
to be adjusted.
will-zdu commented on issue #3635:
URL:
https://github.com/apache/logging-log4j2/issues/3635#issuecomment-2833839839
I know this configuration can avoid this problem, but the question is
whether there is a problem with this default configuration and whether it needs
to be adjusted.
--
T
ppkarwasz commented on issue #3635:
URL:
https://github.com/apache/logging-log4j2/issues/3635#issuecomment-2830090262
@will-zdu,
Depending on the Disruptor waiting strategy you choose a high CPU usage on
the asynchronous thread is perfectly normal. See the [documentation of the
`log
will-zdu commented on issue #3635:
URL:
https://github.com/apache/logging-log4j2/issues/3635#issuecomment-2823808000
com.lmax.disruptor.SleepingWaitStrategy#applyWaitMethod
the default sleepTimeNs to too low，cause the hign cpu usage
--
This is an automated message from the Apache Git S
will-zdu opened a new issue, #3635:
URL: https://github.com/apache/logging-log4j2/issues/3635
## Description
When using Log4j2 in asynchronous logging mode, the CPU usage is
significantly higher than expected, even under low logging throughput. This
issue persists regardless of the c
