<div dir="ltr"><div>Thank you, Matthias!</div><div><br></div><div>The "total payload size of messages in a queue" feature would perfectly suit our needs. I completely understand the low priority of this and the other queue policies; our situation fortunately appears to be an exceedingly unusual one across the community (and tantamount to broker abuse).</div>
<div><br></div><div>By the way - the changes between 2.8.7 and the 3.x releases have been an enormous help to us. RabbitMQ has long been the most reliable part of our architecture, and with every release we find it to be more reliable and easier to configure and monitor. On top of all that, the new features and enhancements have frequently obviated the need for sizeable portions of our applications. Judging by the repository (particularly the bug25553 branch) and other discussions on the mailing list, we can expect even more of that in the future.</div>
<div><br></div><div>That's all to say - thanks guys.</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 10, 2013 at 3:36 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">Joe,<div class="im"><br>
<br>
On 08/07/13 15:28, Joseph Weeks wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is there a way to determine a queue's size in bytes? I'm mostly<br>
interested in size on disk, but the sum of memory and disk would be<br>
sufficient if that happens to be more readily available.<br>
</blockquote>
<br></div>
In general that is impossible, since messages sent to multiple queues are only stored on disk once and their payloads are shared in memory.<br>
<br>
Then there's the added complication that actual memory use of a message<br>
is difficult to work out at best, and impossible if taking into account memory fragmentation and gc effects. on-disk size is quite hard to calculate too.<br>
<br>
Having said that, I suppose we could track the "total payload size of messages in a queue", which would probably suffice for your use case.<br>
<br>
I have just filed a feature request for that. It's not a trivial piece of work though, and we haven't had many requests for this functionality, so I wouldn't expect to see this in a release soon.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On a related note, would it be possible for some future version of<br>
RabbitMQ to allow queue policies like "x-max-length" and "x-message-ttl"<br>
in addition to the queue declaration arguments?<br>
</blockquote>
<br></div>
Yes. It's on our todo list, but not a priority.<br>
<br>
Regards,<br>
<br>
Matthias.<br>
</blockquote></div><br></div>