Talking rates of 10K - 250K msg/sec (messages, not bytes) - those are
impressive numbers in general.
I would be very interested in the system statistics on the broker, and all
of the messaging clients (producers and consumers), as well as the network
links, while this is running. Some resource
> I tried doing this but it seems after 4 consumers the aggregate
consumption throughput does not go up just starts spreading the load across
more consumers.
I have 3 quad core physical machines each on a 1gb link.
In our experience, increasing number of consumers should increase
consumption
Hi Everyone
Thanks for all the feedback. I have put my producer and consumer code and
broker.xml file on a public GitHub repo:
https://github.com/brianr82/artemistesting.git
Please see my replies below.
My reply to Arthur's questions:
> - First, reproduce the problem outside of
While it is possible to improve throughput with batching acks in
transactions, I would recommend to check some other things first. Also
note that transactions can introduce other issues, as I have experienced.
Here are things I recommend to try (forgive me if these have already been
tried):
You can batch acks in transactions.
On Thu, Sep 12, 2019 at 7:14 PM Brian Ramprasad
wrote:
> Hi,
>
> I am trying to improve the throughput of queue Consumers. At present the
> Consumers are much slower than the Producers resulting in messages building
> up inside a queue. From what I can
First you need to identify what kind of consumer you're using (i.e. API &
protocol). The broker supports multiple protocols and each protocol
potentially has multiple client implementations.
Also, please elaborate on:
- how you made your observations and drew your conclusions
- the message
Hi,
I am trying to improve the throughput of queue Consumers. At present the
Consumers are much slower than the Producers resulting in messages building up
inside a queue. From what I can see(maybe I’m wrong) it looks like messages are
sent to consumers of a queue one at a time in a round
