There was some recent work on message priority support for durable subs which puts more pressure on the index for each message send. My suspicion is, that is the cause of the slow down. Unfortunately it is not possible to disable priority ordering at the moment. Can you open a jira issue to track this, we should be able to attain parity with the amqPersistenceAdapter for this use case. I will try and get some time over the next few weeks to investigate further.
On 8 May 2011 06:04, cityjms <[email protected]> wrote: > I switched to amqPersistenceAdapter and got 5X the speed. > > any ideas? > > I was under the impression that KahaDB is the latest/greatest... > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/disk-IO-rate-peak-tp3504958p3506515.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://blog.garytully.com http://fusesource.com
