[
https://issues.apache.org/jira/browse/LOG4NET-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Grabowski resolved LOG4NET-195.
-----------------------------------
Resolution: Later
Thanks for the discussion. There will eventually be an async appender in
log4net. If you have specific questions about log4net performance the
discussion lists are a better place to talk.
> Log4Net Performance comparison with other logging utility
> ---------------------------------------------------------
>
> Key: LOG4NET-195
> URL: https://issues.apache.org/jira/browse/LOG4NET-195
> Project: Log4net
> Issue Type: Test
> Affects Versions: 1.2.10
> Environment: .Net Framework 2.0, VS 2005, Windows XP
> Reporter: Ashish Khandelwal
> Priority: Critical
> Attachments: Log4Net_Vs_nSpring.zip
>
>
> I developed one utility to compare the performance between Log4Net and
> nSpring(another logging utility). The result I saw is surprise to me -
> Log4Net took more time than nSpring. It is surprise because "Log4net claims
> to be fast and flexible: speed first, flexibility second."
> Log4Net says:
> (http://logging.apache.org/log4net/release/manual/internals.html)
> One of the often-cited arguments against logging is its computational cost.
> This is a legitimate concern as even moderately sized applications can
> generate thousands of log requests. Much effort was spent measuring and
> tweaking logging performance. Log4net claims to be fast and flexible: speed
> first, flexibility second.
> Although test is saying Log4Net takes more time, I am still not convinced
> with the result achieved, considering the fact; Log4Net is widely accepted by
> the industry and known for its speed, reliability and flexibility.
> I would like to know why Log4Net is taking more time, we might be missing any
> setting or other which can boost the performance. Can you please help to know
> the reason?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
