[rabbitmq-discuss] vm_memory_high_watermark of RabbitMQ
Matthias Radestock
matthias at rabbitmq.com
Thu Aug 2 23:22:56 BST 2012
On 02/08/12 19:33, Chen, Bin wrote:
> Here is the output of rabbitmqctl status :
>
>
> Status of node rabbit at SERVER001 ...
> [{pid,14920},
> {running_applications,
> [{rabbitmq_management,"RabbitMQ Management Console","2.7.1"},
> {rabbitmq_management_agent,"RabbitMQ Management Agent","2.7.1"},
> {amqp_client,"RabbitMQ AMQP Client","2.7.1"},
> {rabbit,"RabbitMQ","2.7.1"},
> {os_mon,"CPO CXC 138 46","2.2.5"},
> {sasl,"SASL CXC 138 11","2.1.9.3"},
> {rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","2.7.1"},
> {webmachine,"webmachine","1.7.0-rmq2.7.1-hg"},
> {mochiweb,"MochiMedia Web Server","1.3-rmq2.7.1-git"},
> {inets,"INETS CXC 138 49","5.5.2"},
> {mnesia,"MNESIA CXC 138 12","4.4.17"},
> {stdlib,"ERTS CXC 138 10","1.17.3"},
> {kernel,"ERTS CXC 138 10","2.14.3"}]},
> {memory,
> [{total,43200816},
> {processes,13395088},
> {processes_used,7180168},
> {system,29805728},
> {atom,896677},
> {atom_used,872806},
> {binary,10742872},
> {code,7786932},
> {ets,721700}]},
> {vm_memory_high_watermark,0.0333454016734413},
> {vm_memory_limit,858993459}]
> ...done.
>
>
>
> Note that the vm_memory_high_watermark fraction in status report is much
> smaller than 0.4.
Right. That's a bug in the reporting. Doesn't cause any harm otherwise.
As Emile pointed out, if you want to take advantage of all that memory
you have then you need to run the 64 bit version of Erlang, which
evidently you are not:
> {os,{win32,nt}},
> {erlang_version,
> "Erlang R14B02 (erts-5.8.3) [smp:12:12] [rq:12]
> [async-threads:30]\n"},
The 64 bit Windows version of Erlang only became available in R15B, so
you'll need to upgrade and make sure you grab the win64 flavour of the
download (http://www.erlang.org/download/otp_win64_R15B01.exe at present).
While you are at it, you might as well upgrade rabbit to the latest and
greatest 2.8.5.
Regards,
Matthias.
More information about the rabbitmq-discuss
mailing list