Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 21264 invoked from network); 5 Oct 2010 16:08:35 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Oct 2010 16:08:35 -0000 Received: (qmail 1606 invoked by uid 500); 5 Oct 2010 16:08:35 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 1549 invoked by uid 500); 5 Oct 2010 16:08:34 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 1541 invoked by uid 99); 5 Oct 2010 16:08:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Oct 2010 16:08:34 +0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.236.158 is neither permitted nor denied by domain of felix.ehm@cern.ch) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Oct 2010 16:08:27 +0000 Received: from jim.nabble.com ([192.168.236.80]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1P3A3i-0001DG-Dr for users@qpid.apache.org; Tue, 05 Oct 2010 09:08:06 -0700 Date: Tue, 5 Oct 2010 09:08:06 -0700 (PDT) From: felixehm To: users@qpid.apache.org Message-ID: <1286294886423-5603791.post@n2.nabble.com> In-Reply-To: <0A6F5741F32144C181C91E6BD4628899@hope> References: <1286215965015-5600245.post@n2.nabble.com> <0A6F5741F32144C181C91E6BD4628899@hope> Subject: RE: Qpid messaging design MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Steve, thanks for the quick reply. Steve Huston wrote: > > Do you mean you want each client to declare one queue and then bind the > amq.topic exchange to that queue using different routing keys? That > should be possible. > Yes. This is a result from out tests we're run so far. The performance numbers we got were not convincing at all (a 16 Core machine runs flat out using the described way). It seems that the Brokers spend a lot of time dispatching at this (quite high) rate to all the queues. So I assumed that there are more clever ways (e.g. 1 queue/client) to do this and get better results. > If you post the problems you experienced trying to bind 400 keys and one > queue that would be helpful. > Basically its when I try this code : 8-< ------------------------------- /* Declare an exclusive queue on the broker */ string queue = exchange + session.getId().getName(); session.queueDeclare(arg::queue=queue, arg::exclusive=true, arg::autoDelete=true); /* map the bindingkeys to my queue */ for (int i=0; i< subscriptions; i++){ string s = destName + convertInt(i); listener.prepareQueue(queue, exchange, s); } listener.listen(); >-8 ------------------------------ When I try this I get the message : # Subscribing to queue amq.topic6916d790-3d2e-42c0-a826-2fce0811a61c # Subscribing to queue amq.topic6916d790-3d2e-42c0-a826-2fce0811a61c 2010-10-05 17:56:07 warning Exception received from broker: not-allowed: not-allowed: Consumer tags must be unique (qpid/broker/SessionAdapter.cpp:489) [caused by 8 \x04:\x07] not-allowed: not-allowed: Consumer tags must be unique (qpid/broker/SessionAdapter.cpp:489) Cheers, Felix -- View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/Qpid-messaging-design-tp5600245p5603791.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org