Thanks gary,
In our case we are using kaha-db here is the exact config in broker.xml file
We would have expected a drop in throughput may be 30-40%, but not 90%. The
file system that the kaha db directory is pointing to is fairly beefy raid10
local disks.
What we
Thanks for the reply, Gary. We're not doing anything specific
persistence-wise with the messages themselves. Broker-wise, persistence is
enabled on the external broker, but persistence is disabled on the embedded
broker.
I believe this problem occurs regardless of persistence being
enabled/disab
@dan,
Are you using persistent messages?
If yes, typically dispatching is faster than persisting messages and
when the consumers are fast we can by pass storing and syncing to disk
if the consumer acks before the disk write has started. As a result,
through put can be very high.
When we persist,
I have a similar similar setup (flow control turned off)
producer ==> EmbeddedConsumer ==> consumer. Producers producing messages to
kaha persisted topics
In the test setup we have
10 producers per virtual-topic with 10 topics. There are 10 consumers for
each virtual topic
i.e., total of 100 prod
