[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-dev
Subject:    [jira] [Comment Edited] (LOG4J2-163) Create asynchronous Logger for low-latency logging
From:       "Remko Popma (JIRA)" <jira () apache ! org>
Date:       2013-02-25 21:22:13
Message-ID: JIRA.12631163.1360193033607.336293.1361827333221 () arcas
[Download RAW message or body]


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

Remko Popma edited comment on LOG4J2-163 at 2/25/13 9:22 PM:
-------------------------------------------------------------

Maven question:
How do you get Maven to compile AbstractStringLayout.ClassEncoder with JDK6 (in \
package org.apache.logging.log4j.core.layout), and all the other classes with JDK5? I \
have some JDK6-only functionality and would like to do something similar for the \
log4j-async module...  
      was (Author: remkop@yahoo.com):
    Maven question:
How do you get Maven to compile AbstractStringLayout.ClassEncoder with JDK6 (in \
package org.apache.logging.log4j.core.layout), and all the other classes with JDK5? I \
have some JDK6-only functionality and would like to do something similar...  
> Create asynchronous Logger for low-latency logging
> --------------------------------------------------
> 
> Key: LOG4J2-163
> URL: https://issues.apache.org/jira/browse/LOG4J2-163
> Project: Log4j 2
> Issue Type: Improvement
> Affects Versions: 2.0-beta4
> Reporter: Remko Popma
> Attachments: FastLog4j-v2-for-beta4.zip, FastLog4j-v3-for-beta4.zip, \
> FastLog4j-v4-for-beta4.zip 
> 
> One of the main considerations for selecting a logging library is performance, \
> specifically, how long it takes for a call to Logger.log to return. (See the \
> comments of LOG4J-151 for a discussion of latency versus application throughput and \
> logging throughput.) I believe it is possible to improve this performance by an \
> order of magnitude by having an asynchronous Logger implementation that hands off \
> the work to a separate thread as early as possible. The disk I/O would be done in \
> this separate thread.  AsynchAppender is not a good match for these requirements, \
> as with that approach (a) the logging call still needs to flow down the hierarchy \
> to the appender, doing synchronization and creating objects at various points on \
> the way, and (b) when serializing the LogEvent, the getSource() method is always \
> called, which is expensive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]