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 E622E9C3C for ; Thu, 5 Apr 2012 18:54:04 +0000 (UTC) Received: (qmail 47110 invoked by uid 500); 5 Apr 2012 18:54:04 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 47074 invoked by uid 500); 5 Apr 2012 18:54:04 -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 47065 invoked by uid 99); 5 Apr 2012 18:54:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2012 18:54:04 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.250.139 is neither permitted nor denied by domain of saiky76@gmail.com) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2012 18:53:57 +0000 Received: from [192.168.236.139] (helo=joe.nabble.com) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1SFroN-0002nW-M4 for users@activemq.apache.org; Thu, 05 Apr 2012 11:53:35 -0700 Date: Thu, 5 Apr 2012 11:53:35 -0700 (PDT) From: Saiky76 To: users@activemq.apache.org Message-ID: <1333652015677-4535723.post@n4.nabble.com> Subject: Inter Broker overhead is very high MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - we are trying out a POC with Active MQ for extremely high rate of traffic. Our most important goal is the ability to scale. The topology involves topics and for the sake of this post, please consider there is only one consumer per topic. In our reference topology, producers (more than one) keep posting messages to topics to any broker in the cluster of brokers - using the failover protocol that is randomized. Similarly the consumers also attempt to consume messages from any broker in the cluster. Basically, the producers and consumers are not aware of the topic location on a specific broker. For this to work, I set up network bridge (duplex) between the brokers. In tests that had 3 brokers, I ensured all the brokers had a direct network bridge to all other brokers - to ensure there is only one broker hop for the message to be forwarded to the broker on which the topic consumer is listening. The number of connections (both consumers and producers) on a single broker never exceeded 250+. The vertical scaling results for a single broker is quite impressive. But once I try my scaling tests, adding 2 or 3 brokers does not help and the throughput that I got from one broker is exactly the same for the scaling tests with 2 or 3 brokers. The producers and consumers are randomly writing and consuming from the brokers as described above. Actually the load is balanced almost evenly in these writes and consumes. Please note I ensured enough CPU, memory on the consumer side. After doing some analysis, I feel the inter broker communication is responsible. When I tried with 2 brokers and let us say the total number of messages consumed is 200k, then the messages exchanged between 2 brokers is 100k. Similar is the case when 3 brokers are tested - exactly 66% of additional messages are exchanges between brokers. Looks like each broker is doing exactly what is max capable of but the additional power of adding broker is nullified by the network hops. Any ideas, any advise would be great? I am wondering whether horizonatal scalability is actually designed for this. Please note I read the whole of ActiveMq in action book and literature avaialable online on MQ. Please again note the additional network hop is always one and that is predictable. I am trying this on MQ 5.5.1. Thanks. -- View this message in context: http://activemq.2283324.n4.nabble.com/Inter-Broker-overhead-is-very-high-tp4535723p4535723.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.