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 2418B7E95 for ; Wed, 21 Dec 2011 09:14:42 +0000 (UTC) Received: (qmail 58231 invoked by uid 500); 21 Dec 2011 09:14:41 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 58074 invoked by uid 500); 21 Dec 2011 09:14:35 -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 58061 invoked by uid 99); 21 Dec 2011 09:14:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Dec 2011 09:14:32 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of torsten@fusesource.com designates 74.125.245.72 as permitted sender) Received: from [74.125.245.72] (HELO na3sys010aog102.obsmtp.com) (74.125.245.72) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Dec 2011 09:14:24 +0000 Received: from mail-we0-f176.google.com ([74.125.82.176]) (using TLSv1) by na3sys010aob102.postini.com ([74.125.244.12]) with SMTP ID DSNKTvGjWo/eRG7YaO1ZIxD4MJo7GbyFmCbF@postini.com; Wed, 21 Dec 2011 01:14:04 PST Received: by werm10 with SMTP id m10so3661883wer.21 for ; Wed, 21 Dec 2011 01:14:01 -0800 (PST) Received: by 10.216.136.70 with SMTP id v48mr3055437wei.48.1324458841038; Wed, 21 Dec 2011 01:14:01 -0800 (PST) Received: from [192.168.178.31] (p57BD68D9.dip0.t-ipconnect.de. [87.189.104.217]) by mx.google.com with ESMTPS id fi6sm4877072wib.2.2011.12.21.01.13.59 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 21 Dec 2011 01:14:00 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: Backlog data causes producer to slow down. From: Torsten Mielke In-Reply-To: <924C8723-0E88-43C0-82CD-2870DDC7E90B@yahoo-inc.com> Date: Wed, 21 Dec 2011 10:13:57 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <9C3D04DB-9989-4134-8DB1-6B2CD369D763@fusesource.com> References: <924C8723-0E88-43C0-82CD-2870DDC7E90B@yahoo-inc.com> To: users@activemq.apache.org X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org Hard to say what exactly the problem is. In the past I got to learn the = optimizedDispatch=3D"true" isn't always a good choice. Can you try = without it? In addition I recently found that enableIndexWriteAsync=3D"true" on your = kahadb config may not bring any performance improvement. Not sure if you = have set this. Also does your test involve queue or topic messages? Torsten Mielke torsten@fusesource.com tmielke@blogspot.com On Dec 20, 2011, at 10:37 AM, Harish Sharma wrote: > Hi, > I tried to reply to = http://activemq.2283324.n4.nabble.com/Backlog-data-causes-producers-to-slo= w-down-tt3806018.html post . Because i am facing similar issue. > Whenever my consumer goes down and there is a data back log the = production rate goes down significantly. > Moreover when my consumer is up again , the production rate goes down = again and this cycle repeats itself. > Some Info : > I am using ActiveMQ 5.5.1 , KahaDB message store, Producer flow = control =3D FALSE , AsyncSend(true) , persistence =3D true and = ConcurrentQueueStoreAndDispatch =3D true and false (tried both does not = make much difference) > As i read in this post about cursors so i am using the default store = cursor. >=20 > Here is snippet from broker.xml > destinationPolicy> > > > " optimizedDispatch=3D"true" = memoryLimit=3D"1gb" producerFlowControl=3D"false" /> > " optimizedDispatch=3D"true" = memoryLimit=3D"1gb" producerFlowControl=3D"false" /> > > > >=20 > > > > > > > > > > > > > >=20 > I am using all the optimizations(i read from = http://fusesource.com/docs/broker/5.4/tuning/index.html ) > for producer , consumer and broker. > These optimizations are able to increase message production rate a bit = but the main issue is the stability of the production rate.(why it goes = down 10 times and then keep on going down with every time consumers goes = down or goes up again). > I am trying to figure out the cause but unable to pinpoint the code in = activeMQ which is causing this issue. > When i saw threads state in jconsole i found out that as soon as = consumer start running , producer thread goes into wait state ( State: = WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer ).I = understand the queue these producers write to is blocking queue.But i = don't understand why consumers are affecting producers while flow = control is off and my store size is 500 GB and memory is 20GB .Why not = producers are producing at a constant rate until my KahaDB store is = full. >=20 > I really need help in this matter and deeply appreciate any help from = you guys. >=20 > Thanks & Regards > Harish Sharma