Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 95079 invoked from network); 25 Nov 2009 18:45:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Nov 2009 18:45:00 -0000 Received: (qmail 24414 invoked by uid 500); 25 Nov 2009 18:44:59 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 24384 invoked by uid 500); 25 Nov 2009 18:44:58 -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 24370 invoked by uid 99); 25 Nov 2009 18:44:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Nov 2009 18:44:58 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bruce.snyder@gmail.com designates 209.85.220.216 as permitted sender) Received: from [209.85.220.216] (HELO mail-fx0-f216.google.com) (209.85.220.216) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Nov 2009 18:44:56 +0000 Received: by fxm8 with SMTP id 8so8278991fxm.27 for ; Wed, 25 Nov 2009 10:44:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=+AkIXNf8Zs6S+Q0KPmM7Q+dfF/0Ueh2+suJRUgmBHpM=; b=ShA83LbmomwREsV3ZTAI3yrbhclNd/zF9+qiA9mWFdFY0rkpmTWS8ma4/UFZEQeRU3 v9k/LILpoHS2Z68lOI0LMW3Cl6T6ZOePXeSIRtgRGVsLHWH/v/bdseiwEhRy+GUSW1N8 Y97ovvW28inVnkVc+sSn1Y2vjwHw+hJmDakWo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=u/RD0HPu6k+d5n+Fx2+bgM5eskDotlIB7V3YSvOT7XS2lru5bJu8mDP2LvkPb2CzhJ MzCPOG5YvEUgzq2qDW7ZEXjuxmUb/47Sggqt9hB4dt0/bf2xvBw2X8qMcMOLbuQgcz8K BjdZPZpkznB4jjOQDEentEwmkw1BW6kMH2LGg= MIME-Version: 1.0 Received: by 10.223.161.212 with SMTP id s20mr1300698fax.2.1259174674770; Wed, 25 Nov 2009 10:44:34 -0800 (PST) In-Reply-To: <886461EE661A1E45BAA97AF28FAA85DB022CCE1E@barbados.corp.oversee.net> References: <886461EE661A1E45BAA97AF28FAA85DB022CCE1E@barbados.corp.oversee.net> Date: Wed, 25 Nov 2009 11:44:34 -0700 Message-ID: <7b3355cb0911251044p414ade3mceae1fef35367ae6@mail.gmail.com> Subject: Re: Best implementation for reply-request From: Bruce Snyder To: users@activemq.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Nov 25, 2009 at 10:34 AM, Andres Rangel wrote: > Hi, > > We have currently running apache activemq 5.2 in a network of brokers > > > > It has close to 1500 producers and 1200 consumers. > > This producers have =A0each one a temporary queue so that will be 1500 > temp queues in the system. > > > > The reply-request is implemented using temporary queues. > > > > > > I would like to know if there's a performance hit by using temporary > queues instead of using another option. > > > > What do you guys think? There's more overhead involved with such constant creation/destruction of temp queues, but that's it. As long as the broker has been tuned to scale for handling such a large number of destinations, then you should be OK: http://activemq.apache.org/scaling-queues.html Bruce --=20 perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=3D6-E+G-N>61E