[
https://issues.apache.org/jira/browse/LOG4NET-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671415#action_12671415
]
Ashish Khandelwal commented on LOG4NET-195:
-------------------------------------------
Thanks for your response Ron...
Your comment:
It appears that nspring uses background threads to write message to the file.
Log4net does the writing on the same thread by default. I suspect the large
time differences you're seeing is due to the fact that nspring is returning
after it has started the log process...not after all the log entries have
actually been written to the file.
You're trying to compare two unrelated things.
My Question on your comment:
it means, due to Log4Net does the writing on the same thread by default, the
response time from Log4Net is higher and that's why it affects the performance
of Business logic.
I agree that i may be trying to compare two unrelated things. But you know all
together the functionality of both utility is to write logs into the log file.
Whatever design/mechanism they follow, i think the Business logic performance
should not be affected. If it is affecting it means there is problem in the
design.
As you are saying "Log4net does the writing on the same thread by default",
does this mean there is a way to change this default behavior? And/or is there
any way which can boost the performance? Please assist.
Many thanks in advance...
> 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.
