Return-Path: 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 683FB105BB for ; Sat, 1 Mar 2014 00:21:42 +0000 (UTC) Received: (qmail 9643 invoked by uid 500); 1 Mar 2014 00:21:41 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 9560 invoked by uid 500); 1 Mar 2014 00:21:41 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 9552 invoked by uid 99); 1 Mar 2014 00:21:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Mar 2014 00:21:41 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=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.43 as permitted sender) Received: from [209.85.215.43] (HELO mail-la0-f43.google.com) (209.85.215.43) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Mar 2014 00:21:35 +0000 Received: by mail-la0-f43.google.com with SMTP id e16so2952362lan.2 for ; Fri, 28 Feb 2014 16:21:15 -0800 (PST) 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=kCutjbmdAfuieBn8ukAXbRH8dmOVpdw0fYUb3oWGJMY=; b=y65BH6YeG/D/rnFena08rRM4S7caR9MXxmJfp0YNw1dfSPRSpCSvlcUfaFTzK3IEC+ sUs5H8ik6nNx5fdGZsAZwbpqSWKxj+puFp+/Rnka1YmXvynfSPpumPuIYVj8uZ7cC9g/ uca66Ps1QWZNI4C5AZyDsOU1gJU8D5xBe5wn/vX96mZzETsuKRgJMpOcOChFuMD39B/L M9vqOZ54FEFIEdwREjWvrjr0BBmKu+2hdO7enKYgYXhk9a4NHoYrSH23ZO12QagjATmc NsR1Mb9Msd5y1gbIgYrToLvLRKFQwtgLKFeWutShA+HUqZqAJcUlN6OUmHh4mhGd26Es tDbA== MIME-Version: 1.0 X-Received: by 10.152.190.135 with SMTP id gq7mr5363888lac.28.1393633275547; Fri, 28 Feb 2014 16:21:15 -0800 (PST) Received: by 10.114.1.174 with HTTP; Fri, 28 Feb 2014 16:21:15 -0800 (PST) In-Reply-To: References: <1392292184993-4677931.post@n4.nabble.com> Date: Fri, 28 Feb 2014 17:21:15 -0700 Message-ID: Subject: Re: increase Checkpoint interval From: Christian Posta To: "users@activemq.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org i encourage you to take a look at and understand all of the options, but only apply them once you've seen proof (through benchmarking and observations) that they help your situation and solve the bottlenecks you've observed. attempting to tune a broker for performance by switching on options "because they increase performance" is going to land you and your performance in more trouble unless you've proof that what you're doing is alleviating what you're expecting (trust me.. i've been there done that) On Fri, Feb 21, 2014 at 12:33 AM, Yin Wang wrote: > Yes,that help performance but once broker gets restarted,it will take > longer time to complete index recovery. > Here is a guide that may help you to tune performance, > https://access.redhat.com/site/documentation/en-US/JBoss_A-MQ/6.0/html/Tuning_Guide/files/PersTuning-KahaDB.html > > > 2014-02-13 19:49 GMT+08:00 khandelwalanuj : > >> Hey, >> >> I want to increase checkpoint interval of kahadb to store the cache on >> disk. >> By doing this can i increase my broker performance? >> >> Does it has any side effect on broker or any other issues ? >> >> Thanks, >> Anuj >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/increase-Checkpoint-interval-tp4677931.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> -- Christian Posta http://www.christianposta.com/blog twitter: @christianposta