Those log messages are developer debug aids that were added early on in the
dev cycle and possibly should now be removed.
In addition, this one is a little misleading as the cleanup duration is
including the wait time to get exclusive access to the index, and not just
the index cleanup operation duration while it has the lock as it should be.
Are you noticing delays in producers or consumers or just a little worried
about the INFO message?


2009/12/1 neillott <neilmatthewl...@yahoo.com>

>
> Hi,
>
> I know this question was posted earlier, but can anyone help here?
>
> http://old.nabble.com/slow-KahaDB-access-td26172918.html#a26216649
>
> I'm seeing this in my activemq log:
>
> 2009-12-01 09:29:08,690 | INFO  | Slow KahaDB access: cleanup took 9789 |
> org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal
> Checkpoint Worker
> 2009-12-01 09:30:36,376 | INFO  | Slow KahaDB access: cleanup took 1298 |
> org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal
> Checkpoint Worker
> 2009-12-01 09:47:18,871 | INFO  | Slow KahaDB access: cleanup took 14058 |
> org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal
> Checkpoint Worker
>
> When I benchmark the box I'm seeing this:
>
> [myserver] /usr/local/neil/activemq > java -classpath lib/kahadb-5.3.0.jar
> org.apache.kahadb.util.DiskBenchmark
> Benchmarking: /usr/local/neil/activemq/disk-benchmark.dat
> Writes:
>  128000 writes of size 4096 written in 18.521 seconds.
>  6911.0737 writes/second.
>  26.996382 megs/second.
>
> Sync Writes:
>  57936 writes of size 4096 written in 10.001 seconds.
>  5793.0205 writes/second.
>  22.628986 megs/second.
>
> Reads:
>  1960651 reads of size 4096 read in 10.001 seconds.
>  196045.5 writes/second.
>  765.80273 megs/second.
>
>
> What exactly do I need to do to get rid of the slow kahadb access messages?
>
> Thanks,
>
> Neil
> --
> View this message in context:
> http://old.nabble.com/Slow-KahaDB-access-tp26594249p26594249.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

Reply via email to