Hi Malinga,
On Fri, Aug 30, 2013 at 2:42 PM, Malinga Purnasiri malin...@wso2.comwrote:
hi Ishara,
As i remember since per message count increment to DB kill the performance
of MB considerably; we all thought of removing it for the moment. With the
new disruptor changes we thought of
Hi Ishara,
This is great !!!
On Mon, Sep 9, 2013 at 12:30 AM, Ishara Premadasa ish...@wso2.com wrote:
Hi Malinga,
On Fri, Aug 30, 2013 at 2:42 PM, Malinga Purnasiri malin...@wso2.comwrote:
hi Ishara,
As i remember since per message count increment to DB kill the
performance of MB
hi Ishara,
As i remember since per message count increment to DB kill the performance
of MB considerably; we all thought of removing it for the moment. With the
new disruptor changes we thought of updating queue count periodically (not
in real-time). So i think its not good idea to depend on the
Hi,
Did not we increment queue count together with message storing, as a
combined call to Cassandra database? AFAIR we did.
How did it add an additional cost?
If we periodically update queue count we have to be aware of usability
issues.
What abt,
1. Always keep queue count in memory.
2. We
Hi,
Since we have removed the message counters after introducing the disruptor
based message processing for MB 2.1.1 both the above features are
currently not working and we are trying to fix this. As the previous
MessageWriter, implementations from 2.1.0 are no longer used, now we don't
keep
