You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by GitBox <gi...@apache.org> on 2020/05/30 11:14:03 UTC
[GitHub] [logging-log4j2] stepan2271 edited a comment on pull request #361: LOG4J2-2858: More flexible configuration of WaitStrategy of Disruptor
stepan2271 edited a comment on pull request #361:
URL: https://github.com/apache/logging-log4j2/pull/361#issuecomment-636316106
> I put some comments on the mechanics of the proposed changes, but I actually have a bigger question:
>
> what problem are we trying to solve?
> Can you explain the use case where it would help to be able to fine-tune sleep time and number of retries?
What I want to achieve is to log messages with low resource consumption and at the same time garbage free (since I have low latency code in the same JVM with no gc pauses allowed). Currently, I dont see an option that satisfies these requeirements. If I use BlockingWaitStrategy or TimeoutBlockingWaitStrategy then I have garbage. If I use SleepingWaitStrategy with default parameters, YieldingWaitStrategy or BusyspinWaitStrategy then logging consumes resources that I don`t want to allocate there.
If you have any other suggestions on how to handle my use case, I would be happy to use your approach.
----------------------------------------------------------------
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:
users@infra.apache.org