You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Carter Kozak (JIRA)" <ji...@apache.org> on 2019/06/20 12:41:00 UTC

[jira] [Updated] (LOG4J2-2634) AsyncLogger method bytecode should be reduced to 35 bytes for fast inlining

     [ https://issues.apache.org/jira/browse/LOG4J2-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carter Kozak updated LOG4J2-2634:
---------------------------------
    Fix Version/s: 2.12.0

> AsyncLogger method bytecode should be reduced to 35 bytes for fast inlining
> ---------------------------------------------------------------------------
>
>                 Key: LOG4J2-2634
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2634
>             Project: Log4j 2
>          Issue Type: Improvement
>    Affects Versions: 2.11.2
>            Reporter: Carter Kozak
>            Assignee: Carter Kozak
>            Priority: Minor
>             Fix For: 2.12.0
>
>
> Large methods:
> AsyncLogger.logMessage conditional behavior produces a large method, this can be broken into an abstraction which two implementations.
>  
> AsyncLogger.actualAsyncLog can be inlined in cases where Properties are not set
> RingBufferLogEventHandler.onEvent callback notification makes sense in a separate method so that both are below 35b



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)