<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN'>
<html>
<head>
<meta http-equiv='Content-Type' content='text/html;charset=iso-8859-1'>
<style>BODY{font:10pt Tahoma, Verdana, sans-serif;}</style>
</head>
<body>
All I need to do is write the log statement to a file.<br><blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;"><hr><b>From:</b> Thorbjoern Ravn Andersen [mailto:ravn@runjva.com]<br><b>To:</b> slf4j developers list [mailto:dev@slf4j.org]<br><b>Sent:</b> Tue, 28 Apr 2009 10:50:41 -0400<br><b>Subject:</b> Re: [slf4j-dev] Logging Performance<br><br>Ashley Westwell skrev:<br>
> Hey All<br>
><br>
> This may not be the correct place to ask, but I could do with some <br>
> advice. I have an application that needs to output 60,000 (if <br>
> possible) log statements per second (Only the log message no <br>
> formatting). The application has 10 threads that need to log messages <br>
> @ 6,000 per second.<br>
><br>
> Anyone suggest a underlining logging API and what I can do to <br>
> accomplish these numbers?<br>
><br>
> Sorry for the generic request. Any guidance or suggestions would be <br>
> greatly appreciated<br>
Any modern framework should be able to handle that number of requests <br>
throughputwise.<br>
<br>
So the crucial point is: What do you need to do with them?<br>
<br>
<br>
-- <br>
Thorbjørn Ravn Andersen "...plus... Tubular Bells!"<br>
<br>
_______________________________________________<br>
dev mailing list<br>
<a href="mailto:dev@slf4j.org">dev@slf4j.org</a><br>
<a href="http://www.slf4j.org/mailman/listinfo/dev" target="_blank">http://www.slf4j.org/mailman/listinfo/dev</a><br>
</blockquote><style>
</style>
<BR />
<BR />
<HR />
<BR />
Notice: This email is confidential. If you are not the intended recipient, please notify the sender by return email and delete this message from your mail box without reading or copying it or any attachments.<BR />
<BR />
Attention: Ce courriel est confidentiel. Si vous n'êtes pas le destinataire prévu, veuillez en informer l'expéditeur par le courriel de retour et le supprimer immédiatement sans le lire ou le copier (incluant les pièces jointes, le cas échéant).<BR />
</body></html>