You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-user@logging.apache.org by Nicko Cadell <ni...@neoworks.com> on 2006/03/02 20:29:36 UTC

RE: Performance Issues - log4net with Visual Basic 2005

log4net works synchronously and in general this will be the most
performant option. Appenders that talk over the network can introduce
high latencies and for these some form of asynchronous processing may be
more appropriate. 

The costs associated with an appender are not incurred if the appender
is not configured to output the event.

Cheers,
Nicko

> -----Original Message-----
> From: Romil Garg [mailto:RomilG@A-t-g.com] 
> Sent: 07 February 2006 22:54
> To: 'log4net-user@logging.apache.org'
> Subject: Performance Issues - log4net with Visual Basic 2005
> 
> Hi,
> 	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. 
> 
> 
> 
> Thanks.
>