If you have multiple threads that log quite a lot, async logging can make a big difference. If you don't log much, or if the logging is mostly happening on a single thread, I'd suggest sticking with synchronous logging for its simplicity.
Have you thought of any way to measure the performance difference between synchronous and async logging for your application? (If you cannot tell the difference, then what's the point?) :-) If you decide it is worth it, you can switch by changing Root to AsyncRoot and Logger to AsyncLogger in your configuration. On Tue, Aug 7, 2018 at 5:38 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 8/6/2018 10:10 AM, Matt Sicker wrote: > > The %c (aka %logger) pattern uses the logger name. The %C (aka %class) > > pattern does the runtime lookup which kills performance. > > Thank you for that information. I was worried that we had a performance > killing config. What a difference the case of a letter can make! > > I still need information about the best way to switch our config to > Async logging and any other recommendations that come to mind when > reading the config. > > https://apaste.info/MqMq > https://apaste.info/tTcc > > We have a project issue to switch to async: > > https://issues.apache.org/jira/browse/SOLR-12055 > > Is changing the Root tag in the xml to AsyncRoot all we have to do? > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > >
