On 05/17/2013 01:53 PM, Gordon Sim wrote:
On 05/17/2013 01:34 PM, Gordon Sim wrote:
The problem seems mainly confined to the sync publish case at present.
I'll dig into that and send an update.
The problem is that the store is no longer asked to explicitly flush
(and then confirm) the write. This means the broker has to wait until
the periodic flush occurs which causes the degradation in performance.
Many apologies, this was something I broke without noticing it when
refactoring some code. I've raised a JIRA and will get that resolved as
soon as possible: https://issues.apache.org/jira/browse/QPID-4859
Fyi: I have checked a fix in on trunk now and if there is any interest
am happy to post a patch that will apply to 0.20/0.22.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
