Thanks for the notes! �A couple of clarifications:<div><br></div><div>* There aren't really any other applications running on the box -- it's entirely meant for RabbitMQ processing only. �I've run <font face="courier new, monospace">atop</font> during the spikes and no other applications are writing to or reading from the disk. �I've added atop output to the gist if there's additional info there worth noting. �You'll notice that both�RDDSK and WRDSK drop during this spike for the RabbitMQ process.�<a href="https://gist.github.com/3874134" target="_blank" style="color:rgb(17,85,204);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">https://gist.github.com/3874134</a></div>
<div><br></div><div>* Currently we're waiting for the confirm after every publish. �It's not ideal, but it's what we're limited to right now. �We internally "batch" publishes (i.e. we group multiple related messages into a single RabbitMQ message) just due to the reduction in network usage from compression -- is there an additional�batching mechanism supported by the RabbitMQ protocol? (happy to dive into our batches further, but I'm not sure it's related here)</div>
<div><br></div><div>* I'd say there's a pretty constant throughput in the management UI most of the time.</div><div><br></div><div>-Aaron<br><br><div class="gmail_quote">On Tue, Oct 16, 2012 at 7:38 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 16/10/12 12:28, Tim Watson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes they're generally much faster than transactions. Bare in mind<br>
though, that if you're asking for confirms and the messages are<br>
persistent, then you're asking rabbit to fsync to disk repeatedly<br>
which is very expensive. Whether or not this is related to what<br>
you're seeing every 10 minutes is a little unclear to me, though some<br>
of the more knowledgeable rabbits may spot something I've missed<br>
here.<br>
</blockquote>
<br></div>
Nothing in rabbit is scheduled at a ten minute interval.<br>
<br>
I can just about imagine that with a very regular load some ten minute pattern might emerge, but the more likely cause is some other application causing io contention.<br>
<br>
Regards,<br>
<br>
Matthias.<div><div><br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>