I don't think there isn't a comparable option in LevelDB. LevelDB does have an option to delay writes, but that is disabled and not configurable at the moment.
You could try shutting off the cache to your queues which should cause the writes to store to be synchronous: <policyEntry topic="ORDERS.>" useCache="false"> On Wed, Sep 25, 2013 at 2:27 AM, ig-aimia <ian.gara...@aimia.com> wrote: > Hello > > I am currently evaluating performance and reliability of ActiveMQ 5.8.0 and > LevelDB with Amazon AWS EBS volumes and provisioned IOPS, using the > activemq-perftest plugin. Message persistence is of primary importance for > my client. When I run my tests with the broker, producer and consumer, I > see > very little disk activity (vmstat output blocks). When I run the broker and > producer only (no consumers), I see the expected disk activity/output > blocks. > > I'm assuming that the messages are not being persisted in the first > scenario > because of the presence of the active consumers. Is that correct, and if > so, > is it possible to disable this behaviour? I see that using KahaDB as the > persistence adaptor, this feature is managed by the > concurrentStoreAndDispatchQueues parameter. > > ActiveMQ Version: 5.8.0 > Persistence Adaptor: LevelDB > > Regards > Ian > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-Message-Persistence-with-LevelDB-tp4671811.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
