From users-return-9325-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Mon Jun 04 07:40:14 2007 Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 23799 invoked from network); 4 Jun 2007 07:40:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jun 2007 07:40:14 -0000 Received: (qmail 52713 invoked by uid 500); 4 Jun 2007 07:40:18 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 52432 invoked by uid 500); 4 Jun 2007 07:40:17 -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 52421 invoked by uid 99); 4 Jun 2007 07:40:17 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2007 00:40:17 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2007 00:40:11 -0700 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Hv7AN-0007Vo-3I for users@activemq.apache.org; Mon, 04 Jun 2007 00:39:51 -0700 Message-ID: <10945043.post@talk.nabble.com> Date: Mon, 4 Jun 2007 00:39:50 -0700 (PDT) From: Greg Griffin To: users@activemq.apache.org Subject: Re: Are there any figures about ActiveMQ's scalability In-Reply-To: <1B518FD4D3D8AB4C81069F7B79DBC2091F72A2@307622ANEX2.global.avaya.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: nabble@griffinhome.net References: <1B518FD4D3D8AB4C81069F7B79DBC2091F72A2@307622ANEX2.global.avaya.com> X-Virus-Checked: Checked by ClamAV on apache.org I can give you an example from my experience. On a Windows XP, 3.0Ghz dual core, 2GB RAM, with 4.1.1 java, and 2.0.1 CMS (C++ client) average 100 msg/sec with 1,000 topics. 3-4 producers with 6-7 consumers, use no more than 2% of Cpu on the broker, and maybe 1% on each consumer or producer. I've profiled the apps, and the publish and receive take up about 50% of the CPU time, so most of the timing above has to do with ActiveMQ, not anything specific to my app. I've been able to get about 5,000 msg/sec max on topics using one consumer and one producer using all java, with 4 fields in a BytesMessage. Have not dealt with queues. Given the above, it would seem you would be fine with one broker, but depends on the specs of your machine. You can modify the example code quickly to get numbers more specific to your setup. Note that I do see some memory leak on the broker, mentioned in a forum message just after yours: http://www.nabble.com/broker-memory-leak-with-many-topics-tf3845795s2354.html You can also see the example code in this message, to see how to deal with multiple topics, and to reproduce the numbers mentioned above. -- View this message in context: http://www.nabble.com/Are-there-any-figures-about-ActiveMQ%27s-scalability-tf3835059s2354.html#a10945043 Sent from the ActiveMQ - User mailing list archive at Nabble.com.