<div dir="ltr">True - I stand corrected.<br><br>For the purposes of this argument it doesn't really matter, because the persister log is still in the mnesia directory - the point is that the directory should be moved to a separate disk to partition the I/O. If mnesia tables have a great deal of I/O as well, then the persister log itself should be moved somewhere else. The point is also that I/O (and memory, and CPU) should be measured if performance is a concern.<br>
<br>Unfortunately the word "log" has become overloaded. It can mean a log as in a journal, which is what I believe the persister log is, or as a message log, which is what I was referring to. I have seen excessive <i>message</i> logging bring systems to their knees. In many cases, people were unaware that the message logging was even happening. A web server might be logging every single access to a message log, or something else might be running with debug logging turned on. I was just trying to point out that this could be an issue. I know Rabbit has very little message logging by default, except for (at one time) that annoying realm log message.<br>
<br><div class="gmail_quote">On Tue, Sep 23, 2008 at 7:03 PM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Valentino,<br>
<div class="Ih2E3d"><br>
On Tue, Sep 23, 2008 at 11:29 PM, Valentino Volonghi <<a href="mailto:dialtone@gmail.com">dialtone@gmail.com</a>> wrote:<br>
> I'm not sure that rabbit is writing to mnesia for logs.<br>
<br>
</div>It doesn't - the rabbit_persister module handles logging.<br>
<font color="#888888"><br>
Ben<br>
<br>
</font></blockquote></div><br></div>