On 08/02/2016 03:25 PM, Adel Boutros wrote:
How about the tests we did with consumer/producers connected directly to the
dispatcher without any broker where we had 16 000 msg/s with 4 producers. Is it
also a very low value given that there is no persistence or storing here? It
was also synchronous sending.
If you're benchmarking throughput, you really want to avoid synchronous
sending. I think 16K msg/s synchronous with four senders sounds about
right.
Subject: Re: [Performance] Benchmarking Qpid dispatch router 0.6.0 with Qpid
Java Broker 6.0.0
To: users@qpid.apache.org
From: g...@redhat.com
Date: Tue, 2 Aug 2016 20:21:40 +0100
On 02/08/16 20:18, Ted Ross wrote:
Since this is synchronous and durable, I would expect the store to be
the bottleneck in these cases and that for rates of ~7.5K, the router
shouldn't be a factor.
I don't know anything about the java broker internals, but when going
through a router the messages will all be sent down one connection. The
broker will probably then process these serially. That _may_ have a
lower limit than writing to the store from multiple threads in parallel.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
