Have you tried the settings from the example configuration file
conf/activemq-throughput.xml:
<persistenceAdapter>
<kahaDB directory="${activemq.base}/data/kahadb"
enableJournalDiskSyncs="false" indexWriteBatchSize="10000"
indexCacheSize="1000"/>
</persistenceAdapter>
turning off journal disk syncs should have the biggest impact, however
the tradeoff is some reliability since the default (true) is to do a
blocking fsync on every message.
On Fri, May 6, 2011 at 11:39 PM, cityjms <[email protected]> wrote:
> - GC doesn't seem to be an issue
> - threads are under 100
> - publishing connection ranging from 1 to 40 - doesn't affect the result
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/disk-IO-rate-peak-tp3504958p3504962.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
