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. I don't feel competent to answer to that. However, the value we use in Log4j Core are exactly the [same values used by the LMAX Disruptor library](https://github.com/LMAX-Exchange/disruptor/blob/c871ca49826a6be7ada6957f6fbafcfecf7b1f87/src/main/java/com/lmax/disruptor/SleepingWaitStrategy.java#L34-L35): ```java private static final int DEFAULT_RETRIES = 200; private static final long DEFAULT_SLEEP = 100; ``` I wouldn't feel comfortable modifying those values without extensive benchmarks and usage statistics. Values that are perfect for your use case might match the expectations of most Log4j Core **or** might be the exception. It is impossible to say. You can try [proposing a change in the LMAX Disruptor library](https://github.com/LMAX-Exchange/disruptor/issues) directly. If they change the defaults, we will follow their recommendations. -- 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: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
