logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romil Garg <Rom...@A-t-g.com>
Subject RE: Performance Issues - log4net with Visual Basic 2005
Date Tue, 07 Feb 2006 23:16:23 GMT
No, we are not using minimal lock attribute & SMTP appender has not been
rolled out to our test environment yet. So right now we just have Console,
rolling file & event log appenders.
Will it go into SMTP even if minimum threshold is Warn or Fatal.


From: Matthew Brown [mailto:octavius@gmail.com] 
Sent: Tuesday, February 07, 2006 5:07 PM
To: Log4NET User
Subject: Re: Performance Issues - log4net with Visual Basic 2005

Are you by any chance using the MinimalLock attribute?

But out of the last you gave, I would assume SMTP to be the most "blocking"
of all..

On 2/7/06, Romil Garg <RomilG@a-t-g.com <mailto:RomilG@a-t-g.com> > wrote: 

        I am using log4net with Visual Basic 2005 and was wondering if there
are any performance issues with multiple threads of a same process writing
to 1 file. I basically have a process which has a pool of 25 threads doing 
some processing and all these threads write to the same file. Once in  a
while we see some methods taking a little bit longer time than usual. Could
it be because of file being blocked by other threads. Are there any 
performance issues with using associated with this scenario.
We are using Console Appender, Rolling File Appender, Event Log & SMTP
Appenders for Warnings & Fatal Errors.

Does log4net uses threads of its own to write to the log file or is it 
blocking the application thread to wait to write to the file.

I already searched the web but could not find anything concrete.


View raw message