The busy-spin wait strategy is not something I want to promote since it basically dedicates a full core to the logging background thread. It's there mostly for testing and perhaps for hardcore users who are familiar with the Disruptor.
Sent from my iPhone > On 2016/06/14, at 3:24, Matt Sicker <boa...@gmail.com> wrote: > > The code has a case for the busy spin strategy, but it's not listed on this > page: <https://logging.apache.org/log4j/2.x/manual/async.html>. Is this > unsupported or should it be added to the docs? > > -- > Matt Sicker <boa...@gmail.com> --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
