[rabbitmq-discuss] Erlang crashes trying to allocate 583848200 bytes of memory

Dom54 D.Rotondi at Computer.Org
Tue Jan 25 14:03:45 GMT 2011

On Jan 25, 12:44 pm, Dom54 <D.Roto... at Computer.Org> wrote:
perhaps a good news. As announced we are trying to use the same
RabbitMQ version (the last stable one) with the last R14B01 Erlang
The first stress tests seem to work.
We made 2 sets of tests (always using the same test code as indicated
in my previous replies and posted on the RabbitMQ forum), the 1st one
with vm_memory_high_watermark set to 0.25 and the 2nd one at its
default value 0.40.
Both tests seem to work (we run them under Windows Server 2008 R2 64
bit with a 4 GB VM).
In the 1st set we saw a used memory raising up to 512MB (0.25 of 2GB;
I think Erlang is always a 32 bit process, so its max usable address
space is always 2 GB) and them quickly dropping to around 200 MB. I
think the RabbitMQ flow-control mechanism was started and reduced the
pace of the subscriber.
In the 2nd case the memory raised till around 700 MB.

We will due further tests (and compare their speed with similar tests
using ActiveMQ) to finally check if the new Erlang release actually
solve the issue we repoterd.
Thanks to all for their hints and support.

> On Jan 25, 11:44 am, Matthias Radestock <matth... at rabbitmq.com> wrote:
> Hi Matthias,
> > Dom,
> > Dom54 wrote:
> > > To our understanding the RabbitMQ broker (and its supporting
> > > Erlang environment) keeps to be delivered messages in memory; if the
> > > consumer is not fast enough the Erlang memory footprint grows till the
> > > broker crash.
> > The rabbit code does not hold on to messages in memory when it has
> > delivered them to consumers and it is under memory pressure.
> Thats what I stated above. In memory seems to be buffered only
> messages that have not been delivered.
> > But we do rely on the underlying erlang network stack and O/S to tell us
> > when it can't send messages to the consumers. Rather than, say, blindly
> > buffering them. It's possible that therein lies the problem on Windows.
> > Btw, when you tweaked the vm_memory_high_watermark settings, did you
> > check that they were actually taking effect? There is a message near the
> > beginning of the rabbit log file indicating how much memory it is trying
> > to limit itself to.
> Yes we checked the tweak effect in the log file and the log file
> reflects the setting.
> BTW we have just completed another test using a Windows Server 2008 R2
> 64 bit version on a vM with 4 BG RAM, and the problem is still there.
> We are now trying using the last Erlang release (R14B01) instead of
> the R13B03 included in the RabbitMQ distribution, hoping this release
> has fixed some of the problems.
> Thanks, ciao
>    Dom
> > Regards,
> > Matthias.
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > rabbitmq-disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list