Return-Path: 
 <users-return-36196-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-users-archive@www.apache.org
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9BCCA10334
	for <apmail-activemq-users-archive@www.apache.org>;
 Wed, 25 Sep 2013 12:53:06 +0000 (UTC)
Received: (qmail 61214 invoked by uid 500); 25 Sep 2013 12:53:06 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 60675 invoked by uid 500); 25 Sep 2013 12:53:05 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 60667 invoked by uid 99); 25 Sep 2013 12:53:04 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 12:53:04 +0000
X-ASF-Spam-Status: No, hits=2.8 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of christian.posta@gmail.com
 designates 209.85.215.46 as permitted sender)
Received: from [209.85.215.46] (HELO mail-la0-f46.google.com) (209.85.215.46)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 12:53:00 +0000
Received: by mail-la0-f46.google.com with SMTP id eh20so4822186lab.19
        for <users@activemq.apache.org>; Wed, 25 Sep 2013 05:52:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=zfWTB3KAgqxdx8xUICORldlUkkN6Ucm8f9QoSEHF2HQ=;
        b=RIbTd+N5M7PgA76CRFWmU2dNdtUQaaGt93/zwFGyw/DfxdIfuHaBJRNb9C+YlFP6T1
         m6xeUPdsfg7c4Rh6G0aaaQ/xgCSWcAr8ZpyNK68Ucbest5EdXn96CUW7E2cFg9ybIE+h
         JRLrwIhWG4YPTc9bCVxIoZgqSYyrlBPqB99WRT+dCiBnjmJLslr8tZ3leeOLNck5rVeG
         AAmoNvRldc2xMRHdyTKw6fj1ke1u1aWDSVx3ubt4SKUu+zhgpHKQMQb7/FJvpophWJSx
         XOw37So67A4ttYMrd5+JeUbC/RVt97DIEmFAumnkEKVE3jjqyQ2/wJiIDVeiSNWN1mrJ
         M0ng==
MIME-Version: 1.0
X-Received: by 10.152.120.99 with SMTP id lb3mr1791465lab.31.1380113559788;
 Wed, 25 Sep 2013 05:52:39 -0700 (PDT)
Received: by 10.114.2.239 with HTTP; Wed, 25 Sep 2013 05:52:39 -0700 (PDT)
In-Reply-To: <1380101278505-4671811.post@n4.nabble.com>
References: <1380101278505-4671811.post@n4.nabble.com>
Date: Wed, 25 Sep 2013 05:52:39 -0700
Message-ID: 
 <CAKS7T5MdmnnC0kE6zTgYVr=iSOHEu8WJD=SrkTLMfQ1jOfifiw@mail.gmail.com>
Subject: Re: ActiveMQ 5.8 Message Persistence with LevelDB
From: Christian Posta <christian.posta@gmail.com>
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=089e01227ac67b244804e734ba50
X-Virus-Checked: Checked by ClamAV on apache.org

--089e01227ac67b244804e734ba50
Content-Type: text/plain; charset=ISO-8859-1

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.Garaven@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

--089e01227ac67b244804e734ba50--