<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Mathew explained everything with the high memory watermark setting. The
machine is not dedicated to RabbitMQ and is running other things.
Erlang thinks it can have 40% of memory which I guess can go to 80%
before forcing GC. On this machine RabbitMQ crashes well before it
reaches 80% as that much memory is not available.<br>
<br>
I argue that is a poor assumption for a default setting. Nothing should
assume out of the box it can have 80% of physical memory (regardless of
what is running). I hope the new persister takes away some of those
assumptions. It should be smart enough to work with the memory
available. <br>
<br>
David Wragg wrote:
<blockquote cite="mid:k5aasbdg41.fsf@mrbraver.lshift.net" type="cite">
<pre wrap="">Hi Wayne,
Wayne Van Den Handel <a class="moz-txt-link-rfc2396E" href="mailto:wvandenhandel@dataraker.com"><wvandenhandel@dataraker.com></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">Watching top I see RabbitMQ take up more and
more memory over time. It seems that it can only process 30-40k messages
in total/aggregate before it crashes (even though there is never more
than 1000 messages in all queues at one time).
</pre>
</blockquote>
<pre wrap=""><!---->
I wonder if you could boil down your code to a simple consumer and
producer program that demonstrate the problem? We're having trouble
explaining the behaviour you describe, so that would probably be the
best way to get to the bottom of it.
David
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>