[rabbitmq-discuss] Configure VM memory high watermark

CORDIER-AKKA Sylvain (MORPHO) sylvain.cordier.ext at morpho.com
Tue Aug 16 09:27:20 BST 2011

Thank you for this explanation, but I search again a solution about the memory : 
Our RabbitMQ host has got 64GB installed RAM and RabbitMQ server process uses in normal use about 5GB of RAM.
The normal use point is just above the 8% of installed RAM (8% of 64GB is 5.12GB) and a small variation of the use point makes the RabbitMQ starts paging messages and causes a final system slowdown.

If the vm_memory_high_watermark is not the good solution, what are the available solutions?
Increase the amount of installed RAM to 96GB for the system starts paging at 7.68GB? 
Isn't there another way to delay RabbitMQ to start swapping?

Best regards


-----Original Message-----
From: rabbitmq-discuss-bounces at lists.rabbitmq.com [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Matthew Sackman
Sent: Thursday, August 11, 2011 6:23 PM
To: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] Configure VM memory high watermark

On Thu, Aug 11, 2011 at 06:15:45PM +0200, CORDIER-AKKA Sylvain (MORPHO) wrote:
> Following Rabbitmq discuss "unexplained broker shutdown", what are the risks to configure the vm_memory_high_watermark to a higher value in order to not start paging messages at 8% of installed RAM but at 30% or more?

In extremis, it could crash due to the Erlang VM being unable to
allocate sufficient RAM for things like garbage collection. Note this is
really quite unlikely, but not impossible.

Also, Rabbit can't actually stop Erlang from using more RAM. There are
scenarios in which Rabbit will eat up vastly more than the 40% it's
notionally meant to throttle publishers at, so a good amount of buffer
space is well advised. Finally, a good amount of space for the OS to
cache disk in is also helpful.

More likely is that you run out of RAM, which means you then have no
disk cache, so performance will suffer, and then Rabbit will start being
swapped out to disk, which will utterly cripple performance. Once
performance starts to drop, as it's likely Rabbit is overloaded anyway
(otherwise it wouldn't have used up so much RAM), performance will fall
off very rapidly, and this can go from bad to worse.

rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
" Ce courriel et les documents qui lui sont joints peuvent contenir des informations confidentielles ou ayant un caractère privé. S'ils ne vous sont pas destinés, nous vous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque manière que ce soit le contenu. Si ce message vous a été transmis par erreur, merci d'en informer l'expéditeur et de supprimer immédiatement de votre système informatique ce courriel ainsi que tous les documents qui y sont attachés."
" This e-mail and any attached documents may contain confidential or proprietary information. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. If you have received this e-mail in error, please advise the sender immediately and delete this e-mail and all attached documents from your computer system."

More information about the rabbitmq-discuss mailing list