logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Smith <paul.sm...@lawlex.com.au>
Subject Re: Thinking about log4j performance
Date Thu, 11 Dec 2003 20:40:46 GMT
In almost all cases this is correct, the logging done to the appender is
all done within the same thread.

Only the AsyncAppender performs it's appending in a separate thread.

regards,

Paul Smith

On Thu, 2003-12-11 at 19:32, Yu Xiang Xi (Maveo) wrote:
> It's known that log4j has a good performance even 'on an AMD Duron clocked
> at 800Mhz running JDK 1.3.1' machine.
> 
> If I have lot of appenders, for example, a socket appender, which will cost
> 0.1 second to communicate with the socket server, and there's still a file
> appender in the system all the same.
> 
> My puzzle is that, will socket appender and file appender work at the same
> time?
> Or run socket appender first, and AFTER socket appender done, file appender
> later.
> And the system will hold on till all the appenders are invoked?
> 
> Might it can be explained in the below assumption codes.
> Assumption
> ....
> methodA();                      //(1)
> logger.debug("hello,log4j")     //(2) hold on till all appenders are invoked
> one by one?
> methodB();                      //(3)
> ....
> 
> Best Regards
> Xi Yuxiang
> System Architect
> Maveo Systems Limited - www.maveosystems.com
> Email: yxxi@maveosystems.com 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org


Mime
View raw message