[rabbitmq-discuss] another performance question

[Geib, Mark]

Mathias,

This is a debian wheezy box. I installed erlang from the debian repo, i.e. apt-get install erlang I think. Erlang is R15B01. We do have a number of rabbitmq installs on various boxes and different versions of erlang, etc. I have tried this at least three different boxes with similar results. On a beefy VM on new fast hardware I see about 23-25kHz compared to the 15kHz I reported to you. In all cases everything is running local, no lan network issues to consider. We generally run debian or ubuntu installs with very little if any changes. In all my testing this morning using your example command I never see anything close to what you reported. 25kHz is the absolute max I see on that shinny new VM.


The output from rabbitmqctl status is

Status of node 'rabbit at geib-2950' ...
[{pid,7926},
 {running_applications,
     [{rabbitmq_management,"RabbitMQ Management Console","3.1.3"},
      {rabbitmq_management_agent,"RabbitMQ Management Agent","3.1.3"},
      {rabbit,"RabbitMQ","3.1.3"},
      {os_mon,"CPO  CXC 138 46","2.2.9"},
      {rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","3.1.3"},
      {webmachine,"webmachine","1.9.1-rmq3.1.3-git52e62bc"},
      {mochiweb,"MochiMedia Web Server","2.3.1-rmq3.1.3-gitd541e9a"},
      {xmerl,"XML parser","1.3.1"},
      {inets,"INETS  CXC 138 49","5.9"},
      {mnesia,"MNESIA  CXC 138 12","4.7"},
      {amqp_client,"RabbitMQ AMQP Client","3.1.0"},
      {sasl,"SASL  CXC 138 11","2.2.1"},
      {stdlib,"ERTS  CXC 138 10","1.18.1"},
      {kernel,"ERTS  CXC 138 10","2.15.1"}]},
 {os,{unix,linux}},
 {erlang_version,
     "Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:8:8] [async-threads:30] [kernel-poll:true]\n"},
 {memory,
     [{total,38421704},
      {connection_procs,5408},
      {queue_procs,5408},
      {plugins,571680},
      {other_proc,11268840},
      {mnesia,60696},
      {mgmt_db,59384},
      {msg_index,605640},
      {other_ets,1213728},
      {binary,1413144},
      {code,18526191},
      {atom,703377},
      {other_system,3988208}]},
 {vm_memory_high_watermark,0.4},
 {vm_memory_limit,13524641382},
 {disk_free_limit,1000000000},
 {disk_free,1067746856960},
 {file_descriptors,
     [{total_limit,924},{total_used,3},{sockets_limit,829},{sockets_used,1}]},
 {processes,[{limit,1048576},{used,202}]},
 {run_queue,0},
 {uptime,7879}]
...done.

Mark Geib
Principal Engineer
Cheyenne Software Engineering
mark.geib at echostar.com / 35-215


“We, the unwilling, led by the unknowing, are doing the impossible for the ungrateful. We have done so much, for so long, with so little, we are now qualified to do anything with nothing.” 
― Mother Teresa


On Jul 17, 2013, at 1:40 PM, Matthias Radestock wrote:

> Mark,
> 
> On 17/07/13 16:07, Geib, Mark wrote:
>> I just ran the same, version 3.1.3 java client against my 3.1.1-1 broker.
>> 
>> sh runjava.sh com.rabbitmq.examples.MulticastMain -y 0 -t topic -s 10000
>> starting producer #0
>> [...]
>> time: 15.017s, sent: 16091 msg/s
> 
> How did you install Erlang? And what version gets reported in 'rabbitmqctl status'?
> 
> TBH I suspect this is an O/S level issue. Have you got any rabbits running elsewhere that you can compare the performance with?
> 
> Matthias.
>