On Mon, Feb 24, 2014 at 11:19 PM, Brent <[email protected]> wrote: > Log4J2 is. I recently stumbled across this link > http://logging.apache.org/log4j/2.x/manual/async.html > where they claim spectacular results. In particular, Log4J2's AsyncLogger > blows away Logback's AsyncAppender. > > It looks like several people have done their own experiments to have > Logback use Disruptors for aynchronous logging. For example: > https://github.com/reactor/reactor/tree/master/reactor-logback > And this guy posted his results on Logback's user email list: > http://mailman.qos.ch/pipermail/logback-user/2013-August/004201.html > > I would like to know if there are any official plans to incorporate LMAX's > Disruptor (or some equivalent) technology in Logback. I searched this > list, and could find no discussion. > > No official plans yet, but I'm interested in incorporating it. We recently mentioned Disruptor briefly in [1].
[1] https://github.com/qos-ch/logback/pull/170 > From my perspective, this is critical: fast asynchronous logging is of > extreme importance for my current employer, and I bet many other people too. >
_______________________________________________ logback-dev mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-dev
