You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2022/01/17 21:30:00 UTC

[jira] [Commented] (LOG4J2-1870) Add a "fast defaults" option to make modern configurations simpler

    [ https://issues.apache.org/jira/browse/LOG4J2-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477428#comment-17477428 ] 

Matt Sicker commented on LOG4J2-1870:
-------------------------------------

This might be a good idea to incorporate for 3.0 as the new default configuration.

> Add a "fast defaults" option to make modern configurations simpler
> ------------------------------------------------------------------
>
>                 Key: LOG4J2-1870
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1870
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Matt Sicker
>            Priority: Major
>
> There have been a few non-default options added over various releases which improve the performance of Log4j. These include:
> * Async loggers
> * Direct console appender
> * Async Kafka appender
> This feature should add a Log4j system property to quickly enable fast defaults instead of the backward compatible ones. This should enable async loggers globally when the LMAX library is available. This should also enable current and future fast options to appenders and other plugins.
> Ideally, this feature should be accompanied by an explanation of how to choose options and appenders for difference scenarios. For example, it would be great to explain why a user might use different wait strategies in different scenarios (high throughput versus low latency versus safety), or why using different clocks than the default can be useful. Explicit details of all available options should remain on their normal manual pages, but quick summaries and pointers on such a page would be useful.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)