the difference is in fsync behavior of the two systems. Some drive/OS
combinations do not actually go to the disk, others do.
There is a little utility in kahaDB from 5.3 that will demonstrate the
raw disk performance w.r.t fsync and you can compare the two systems.
java -classpath lib/kahadb-5.3.0.jar org.apache.kahadb.util.DiskBenchmark
by default it writes to a file in the current directory and spits out
results you can compare.
2009/11/5 KimSchneider <
kim.schneider@...>:
>
> We get the same messages on two different ubuntu servers. There is no load on
> the servers and no producers connected to activemq but cleanups take from
> 500 to 2000.
>
> This doesn't happen on my developer pc (windows) and I wonder why?!
>
> Anyone's got a solution for this?
>
>
>
> Matthew Hixson wrote:
>>
>> I see these messages scroll up the console:
>>
>> INFO | Slow KahaDB access: cleanup took 1998
>>
>
> --
> View this message in context:
http://old.nabble.com/slow-KahaDB-access-tp26172918p26213644.html> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
http://blog.garytully.comOpen Source Integration
http://fusesource.com