[rabbitmq-discuss] Feature Req / Bug list

Fri Oct 25 17:13:00 BST 2013

On Fri, Oct 25, 2013 at 3:37 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> First of all, thank you for taking the time to generate a test case. I
> haven't reproduced anything yet, but rest assured that I will attempt to do
> so.
>
> I do have some quibbles with a couple of your assertions though:

Great! Part of this conversation is to help me get up to speed quickly on
rabbit internals and architecture, since I'm relatively new to it, and
we're in the middle of deploying it for a bunch of different uses. So,
please correct me if I've misunderstood its behaviour or design. :)

> -rabbitmq_management listener [{port,4444$n},{redirect_old_port,false}]
>
> This redirect port will be going away in 3.3.0.
>
>
Ahhh, this does make sense, and you're right, it doesn't seem to have an
adverse affects on cluster operations.

Err, your script invokes amqp-publish(1) in a loop. 100,000 times. I
> suspect most of the slowness is due to the time taken to fork that many
> processes, open and close that many AMQP connections, and so on. I would
> guess this goes faster on an SSD because you can fork() faster.
>

Hmmm... I wouldn't expect this to be the case, since I can fork 100000
echos is about 1s on this box. I am willing to admit that there could be
issues in the way the data's being generated out of bash, or for any number
of other reasons though. However, we did see a cluster of 5 machines backed
by 7200 RPM disks get swamped with IO unexpectedly early, which is the
issue I'm trying to reproduce, so I'll work harder on a better test case.

> Certainly I can populate 100 queues with 1,000 messages each in a rather
> small fraction of a second with the PerfTest tool (
> http://www.rabbitmq.com/java-tools.html) if the same message goes to all
> queues 1,000 times, or in less than 10 seconds if each message is distinct.
>

Good to know. I'll be sure to use this when I rework this test case.

Graeme
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131025/87fe9317/attachment.htm>