log4perl-devel

[log4perl-devel] Log4perl best practices for high traffic sites

[Trevor L. <tl...@we...>]

Hi,
   I'm adding logging to a high-traffic mod_perl website and am worried  
about the performance penalties of writing stuff to disc on every request.  
In production, we'd probably only be logging a few lines per request. I'm  
wondering what the common usage of log4perl is like in these situations.  
I've seen suggestions for piping messages to a message bus with something  
like Log::Log4perl::Appender::Spread, but I'd love to hear what the  
experiences of people on this list have been when deploying log4perl on  
high traffic sites. What's worked, what hasn't? Is anyone logging directly  
to a database?

Thanks in advance for your insight,

Trevor

Re: [log4perl-devel] Log4perl best practices for high traffic sites

[Mike S. <m...@pe...>]

On Wed, 20 Jan 2010, Trevor Little wrote:

>   I'm adding logging to a high-traffic mod_perl website and am worried
>   about the performance penalties of writing stuff to disc on every
>   request.

It depends on your traffic numbers. I've found that a file appender
works quite well up to 1000 reqs/sec because the OS typically caches
disc access quite efficiently. Your mileage might vary, so prudent load
testing is of the essence.

-- Mike

Mike Schilli
m...@pe...