If your primary concern is latency, testing with a maxed-out message
rate (which it seems is what you are doing) will give very dubious
results. Maxing out the message rate means that all internal buffers are
full, and thus messages take a while to get through the broker.
The same is presumably true for ActiveMQ, but presumably it has smaller
buffers.
This is even more true if your tests are able to publish messages faster
than they consume (which I guess is what's happening in your last row) -
if your test ends up enqueueing messages and then taking a while to
dequeue them then I am not surprised you see high latency.
Dropping your message rate to even 90% of the maximum will give huge
latency gains - see the final chart here:
http://www.rabbitmq.com/blog/2012/04/17/rabbitmq-performance-measurements-part-1/Finally, I would be wary of constructing a synthetic benchmark and then
using it to pick which product you go with, unless you determine that
one product has acceptable performance and others do not. Factors such
as reliability, ease of use, feature set and so on tend to be more
important than a 10% difference in performance.
Hopefully I would still be saying that even if RabbitMQ were "winning"
your tests :-)
Cheers, Simon
On 18/06/13 04:00, JC wrote:
> Hi,
>
> We are in the process of evaluating middleware and choosing which
> middleware we pick for a potentially large scale distributed
> application. We did an evaluation between activemq and rabbitmq with
> different test cases. So far activemq has outperformed rabbitmq using
> the default out-of-box configuration especially on the latency side.
> We use activemq openWire protocol vs. rabbit AMQP, Here is one example
> result of the test we did on 1 publisher/1 consumer and we measure the
> latency from send to receive time. Similar results we get from
> multiple consumers as well. Any one has done the similar benchmark?
> Could you please share your experience? And if anyone knows the tips to
> boost rabbitmq performance, please let us know. The rabbit test client
> is using fanout exchange and MINIMAL_BASIC to publish messages.
>
> BrokerType Publishers Consumers SlowConsumers TgtMsgRate(mps)
> TgtMsgLimit AvgMsgSentRate(mps) AvgSentTime(ns) AvgMsgRcvRate(mps)
> MinLat(ns) MaxLat(ns) AvgLat(ns) MedLat(ns) 90%Lat(ns)
> Activemq@middlewarebench 1 1 0 25000 1000000 20776 5644 20776
> 99484 7959080 259337 255760 316848
> Rabbit@middlewarebench 1 1 0 25000 1000000 20749 5440 20749
> 171994 46140955 870211 913283 988979
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Activemq@middlewarebench 1 1 0 100000 1000000 62695 5347 62695
> 100634 19872040 491588 359763 510862
> Rabbit@middlewarebench 1 1 0 100000 1000000 56850 6790 54512
> 315808 822398215 487403726 487170082 696265654
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
>
[hidden email]
>
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
--
Simon MacMullen
RabbitMQ, Pivotal
_______________________________________________
rabbitmq-discuss mailing list
[hidden email]
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Locked
