[jira] [Comment Edited] (LOG4NET-83) Allow flushing into file every X milliseconds

["Robert Sevcik (JIRA)" <ji...@apache.org>]

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

Robert Sevcik edited comment on LOG4NET-83 at 6/23/14 8:54 PM:
---------------------------------------------------------------

I called it Keep-alive appender (KeepAliveAppender). It's implemented in log4net.Ext.Json for now. I'm hopeful it will get accepted into log4net trunk.

https://sourceforge.net/p/log4net-json/wiki/keep-alive%20appender/


was (Author: robajz):
I called it Keep-alive appender (KeepAliveAppender) now. It's implemented in log4net.Ext.Json for now. I'm hopeful it will get accepted into log4net trunk.

https://sourceforge.net/p/log4net-json/wiki/keep-alive%20appender/

> Allow flushing into file every X milliseconds
> ---------------------------------------------
>
>                 Key: LOG4NET-83
>                 URL: https://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
>             Fix For: 1.2 Maintenance Release
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)