That was it. Thanks!
I had to set to indexCacheSize = 10 to get the performance I'm looking
for.
rajdavies wrote:
>
> ok - it looks like you might need to tune KahaDB - set the
> indexCacheSize = 1000 - see http://activemq.apache.org/kahadb.html
>
>
>
--
View this message in conte
of indexing
messages once you start to consume from topic.
rajdavies wrote:
>
> could you provide a test case ?
>
> cheers,
>
> Rob
> On 11 Feb 2010, at 21:41, rideallday wrote:
>
>>
>> Umm, actually I'm still seeing issues with high Index tim
Umm, actually I'm still seeing issues with high Index times for topics.
My test case is:
Send a huge amount of messages into the broker. Let several hundred thousand
accumulate. Then start consumers and see how long it takes to drain the
queues and topics.
The result is:
For queues- excellent.
I can confirm that has resolved the issue I was seeing. Thanks Rob!
What's ETA for 5.4 or applying this fix in 5.3? I'll need an official stable
release to put into production.
--
View this message in context:
http://old.nabble.com/OOM-with-high-KahaDB-index-time-tp27217704p27413891.html
Sent
I believe this meets the majority of your requirements:
http://activemq.apache.org/how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages-.html
Using KahaDB as a persistent store gets flaky for me after 30K or so
messages. Indexing takes way too long and happens every second. I g
I went back to AMQStore. Working fine for me.
--
View this message in context:
http://old.nabble.com/OOM-with-high-KahaDB-index-time-tp27217704p27249114.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
rajdavies wrote:
>
> FileCursor and Kaha (which is
> used by the AMQStore). - can you share the configuration you are using?
> KahaDB isn't the same as Kaha
>
I'm still unsure... I'm using KahaDB, not AMQStore. I was about to go back
to AMQStore as this setup just isn't working, but I reall
Rob,
I'm seeing the exact same behaviour as Daniel,
>
> So I would recommend the following
>
> 2. Try KahaDB - which - with the BTreeIndex - will not hit the
> problems you are seeing with the Filecursor
>
>
however I am already using KahaDB as the persistenceAdapter.
Your advice seem
I am also seeing these. I understand that you can set a thrreshold to stop it
logging, but it seems that things slow down or stall while KahaDB performs
an index. Ie- consumers of this broker are blocked waiting for the index to
complete.
This happens when my message store grows to several thousa
