[jboss-jira] [JBoss JIRA] (WFCORE-249) Wrap the default logging handlers in an AsyncHandler

[James Perkins (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins closed WFCORE-249.
--------------------------------
    Resolution: Rejected


I don't see much benefit in this. If anyone disagrees please feel free to reopen.

> Wrap the default logging handlers in an AsyncHandler
> ----------------------------------------------------
>
>                 Key: WFCORE-249
>                 URL: https://issues.jboss.org/browse/WFCORE-249
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Logging
>            Reporter: Kyle Lape
>            Assignee: James Perkins
>
> This change could potentially enhance performance under heavier logging loads, but the the disadvantages probably need to be considered first.
> * Under light logging load, is performance improved much?
> * How about under medium load?
> * Under heavy load, the async queue may overflow, causing either one of two sceanrios:
> ** {{OverflowAction.DISCARD}}: The loss of messages.  Probably not the right choice for default.
> ** {{OverflowAction.BLOCK}}: Threads block until queue clears.  Could be argued that async is not much better than plain synchronous logging in this scenario.
> * If the aync thread crashes, are messages lost?  If so, is this much worse than synchronous logging, and how often can an async thread crash?



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)