[rabbitmq-discuss] memory usage reporting
Kyle O'Donnell
kyleo at 0b10.mx
Wed Apr 24 21:49:46 BST 2013
R16B seems to behave the same way R15B03 does:
Status of node 'rabbit at p1-amqp-j101' ...
[{pid,21245},
{running_applications,
[{rabbitmq_management_visualiser,"RabbitMQ Visualiser","0.0.0"},
{rabbitmq_management,"RabbitMQ Management Console","0.0.0"},
{rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","0.0.0"},
{webmachine,"webmachine","1.9.1-rmq0.0.0-git52e62bc"},
{mochiweb,"MochiMedia Web Server","2.3.1-rmq0.0.0-gitd541e9a"},
{rabbitmq_management_agent,"RabbitMQ Management Agent","0.0.0"},
{rabbit,"RabbitMQ","3.0.4"},
{mnesia,"MNESIA CXC 138 12","4.8"},
{os_mon,"CPO CXC 138 46","2.2.11"},
{inets,"INETS CXC 138 49","5.9.4"},
{amqp_client,"RabbitMQ AMQP Client","0.0.0"},
{xmerl,"XML parser","1.3.3"},
{sasl,"SASL CXC 138 11","2.3.1"},
{stdlib,"ERTS CXC 138 10","1.19.1"},
{kernel,"ERTS CXC 138 10","2.16.1"}]},
{os,{unix,linux}},
{erlang_version,
"Erlang R16B (erts-5.10.1) [source] [64-bit] [smp:4:4] [async-threads:30] [hipe] [kernel-poll:true]\n"},
{memory,
[{total,15478231776},
{connection_procs,92186808},
{queue_procs,16649120},
{plugins,465008},
{other_proc,6397291},
{mnesia,2538008},
{mgmt_db,24607160},
{msg_index,386144},
{other_ets,3307440},
{binary,15285217656},
{code,21554477},
{atom,801697},
{other_system,24120967}]},
{vm_memory_high_watermark,0.4},
{vm_memory_limit,13496687001},
{disk_free_limit,1000000000},
{disk_free,21794127872},
{file_descriptors,
[{total_limit,130970},
{total_used,1828},
{sockets_limit,117871},
{sockets_used,1826}]},
{processes,[{limit,1048576},{used,20871}]},
{run_queue,0},
{uptime,329}]
...done.
----- Original Message -----
From: "Matthias Radestock" <matthias at rabbitmq.com>
To: "Kyle O'Donnell" <kyleo at 0b10.mx>
Cc: "Discussions about RabbitMQ" <rabbitmq-discuss at lists.rabbitmq.com>
Sent: Wednesday, April 24, 2013 2:48:11 PM
Subject: Re: [rabbitmq-discuss] memory usage reporting
Kyle,
On 24/04/13 18:49, Kyle O'Donnell wrote:
> The difference is actually that my application finished starting
> using rabbit with R14 whereas with R15 my application didn't get to
> start because rabbit had reached the high watermark.
I see. There could be some sort of feedback loop between your app and
rabbit, where some behaviour difference in the underlying Erlang VM gets
amplified.
> Rabbit is not the first erlang app I've seen to use large amounts of
> Virtual Memory when used with R15. I am still leaning more towards
> R15, but haven't found any proof yet.
Give R16B a try.
Regards,
Matthias.
More information about the rabbitmq-discuss
mailing list