From users-return-28788-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Mon Sep 12 00:09:21 2011 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 501C88170 for ; Mon, 12 Sep 2011 00:09:21 +0000 (UTC) Received: (qmail 47748 invoked by uid 500); 12 Sep 2011 00:09:20 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 47591 invoked by uid 500); 12 Sep 2011 00:09:19 -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 47575 invoked by uid 99); 12 Sep 2011 00:09:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Sep 2011 00:09:19 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of bhupesh@groupon.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Sep 2011 00:09:12 +0000 Received: from joe.nabble.com ([192.168.236.139]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1R2u4y-0004Hm-03 for users@activemq.apache.org; Sun, 11 Sep 2011 17:08:52 -0700 Date: Sun, 11 Sep 2011 17:08:51 -0700 (PDT) From: bbansal To: users@activemq.apache.org Message-ID: <1315786131978-3806018.post@n4.nabble.com> Subject: Backlog data causes producers to slow down. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello folks, I am evaluating ActiveMQ for some simple scenarios. The web-server will push notifications to the queue/topic to be consumed by one or many consumers. The one requirement is web-server should not get impacted or should be able to write at their speed even if consumers goes down etc. ActiveMQ is performing very well with about 1500 QPS (8 producer thread, persistence, kaha-db) Kahadb parameters being used are enableJournalDiskSyncs="false" indexWriteBatchSize="1000" enableIndexWriteAsync="true The system works great if consumers are all caught up, the issue is when I am trying to test scenarios with backlogged data (keep running producer for 30 mins or so) and then start consumers. Consumer show good consumption rate but the producers (8 threads same as before) cannot do more than 120 QPS. This is a drop of more than 90% degradation. I ran profiler on the code (Jprofiler) and looks like the writers are getting stuck for write locks while competing with the removeAsyncMessages() or call to clear messages which got acknowledged from clients etc. I saw similar complaints for some other folks, Is there some settings we can use to fix the problem ? I dont want to degrade any guarantee level (eg. disable acks etc). Would be more than happy to run experiments with different settings if folks have some suggestions. -- View this message in context: http://activemq.2283324.n4.nabble.com/Backlog-data-causes-producers-to-slow-down-tp3806018p3806018.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.