You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Tal G (JIRA)" <ji...@apache.org> on 2006/07/25 09:10:13 UTC
[jira] Created: (LOG4NET-83) Allow flushing into file every X
milliseconds
Allow flushing into file every X milliseconds
---------------------------------------------
Key: LOG4NET-83
URL: http://issues.apache.org/jira/browse/LOG4NET-83
Project: Log4net
Issue Type: New Feature
Components: Appenders
Affects Versions: 1.2.10
Environment: All
Reporter: Tal G
Priority: Minor
In FileAppender you can specify either immediate flush on every message or not flushing at all.
Immediate flushing reduces performance in 10% - 20%, but when flushing is skipped, then it is likely that the last few log events will not be recorded on disk when the application exits.
I suggest adding a parameter that flushes to file every X millisecond. In this case you will gain most of the 10%-20% performance, and you will minimize the lost of logs when the application exits.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (LOG4NET-83) Allow flushing into file every X
milliseconds
Posted by "Ron Grabowski (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LOG4NET-83?page=comments#action_12423487 ]
Ron Grabowski commented on LOG4NET-83:
--------------------------------------
When the application is ending and log4net is shutting down the appenders are flushed. A more general solution would be to write an appender that accepts a BufferedAppender (or more than one BufferedAppenders) and calls flush at the appropriate interval.
> Allow flushing into file every X milliseconds
> ---------------------------------------------
>
> Key: LOG4NET-83
> URL: http://issues.apache.org/jira/browse/LOG4NET-83
> Project: Log4net
> Issue Type: New Feature
> Components: Appenders
> Affects Versions: 1.2.10
> Environment: All
> Reporter: Tal G
> Priority: Minor
>
> In FileAppender you can specify either immediate flush on every message or not flushing at all.
> Immediate flushing reduces performance in 10% - 20%, but when flushing is skipped, then it is likely that the last few log events will not be recorded on disk when the application exits.
> I suggest adding a parameter that flushes to file every X millisecond. In this case you will gain most of the 10%-20% performance, and you will minimize the lost of logs when the application exits.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (LOG4NET-83) Allow flushing into file every X
milliseconds
Posted by "Tal G (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LOG4NET-83?page=comments#action_12423540 ]
Tal G commented on LOG4NET-83:
------------------------------
I am talking about application that crashed, so it didn't make shutdown.
FileAppender is not a BufferedAppender so how will it work?
> Allow flushing into file every X milliseconds
> ---------------------------------------------
>
> Key: LOG4NET-83
> URL: http://issues.apache.org/jira/browse/LOG4NET-83
> Project: Log4net
> Issue Type: New Feature
> Components: Appenders
> Affects Versions: 1.2.10
> Environment: All
> Reporter: Tal G
> Priority: Minor
>
> In FileAppender you can specify either immediate flush on every message or not flushing at all.
> Immediate flushing reduces performance in 10% - 20%, but when flushing is skipped, then it is likely that the last few log events will not be recorded on disk when the application exits.
> I suggest adding a parameter that flushes to file every X millisecond. In this case you will gain most of the 10%-20% performance, and you will minimize the lost of logs when the application exits.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira