Hi Stan Yes, I have this on, plus optimized dispatches and async send on the publisher side....
Also tried the sample activemq code to make sure it isn't my code. On May 7, 2011, at 8:25, "Stan Lewis [via ActiveMQ]"<[email protected]> wrote: > 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 <[hidden email]> 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. > > > > > If you reply to this email, your message will be added to the discussion > below: > http://activemq.2283324.n4.nabble.com/disk-IO-rate-peak-tp3504958p3505401.html > To unsubscribe from disk IO rate peak?, click here. -- View this message in context: http://activemq.2283324.n4.nabble.com/disk-IO-rate-peak-tp3504958p3505584.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
