From qpid-users-return-415-apmail-incubator-qpid-users-archive=incubator.apache.org@incubator.apache.org Wed Nov 12 18:04:47 2008 Return-Path: Delivered-To: apmail-incubator-qpid-users-archive@locus.apache.org Received: (qmail 16528 invoked from network); 12 Nov 2008 18:04:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Nov 2008 18:04:47 -0000 Received: (qmail 62975 invoked by uid 500); 12 Nov 2008 18:04:45 -0000 Delivered-To: apmail-incubator-qpid-users-archive@incubator.apache.org Received: (qmail 62943 invoked by uid 500); 12 Nov 2008 18:04:45 -0000 Mailing-List: contact qpid-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: qpid-users@incubator.apache.org Delivered-To: mailing list qpid-users@incubator.apache.org Received: (qmail 62921 invoked by uid 99); 12 Nov 2008 18:04:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Nov 2008 10:04:45 -0800 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 (athena.apache.org: domain of cctrieloff@redhat.com designates 66.187.237.31 as permitted sender) Received: from [66.187.237.31] (HELO mx2.redhat.com) (66.187.237.31) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Nov 2008 18:03:27 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id mACI49b5019604; Wed, 12 Nov 2008 13:04:09 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id mACI48qX010623; Wed, 12 Nov 2008 13:04:08 -0500 Received: from localhost.localdomain (dhcp-100-18-96.bos.redhat.com [10.16.18.96]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id mACI45lw013499; Wed, 12 Nov 2008 13:04:05 -0500 Message-ID: <491B19AE.4040806@redhat.com> Date: Wed, 12 Nov 2008 13:00:14 -0500 From: Carl Trieloff Reply-To: cctrieloff@redhat.com Organization: Red Hat User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: gregory james marsh CC: qpid-dev@incubator.apache.org, "qpid-users@incubator.apache.org" Subject: Re: AMQP Paper, using Qpid References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.58 on 172.16.27.26 X-Virus-Checked: Checked by ClamAV on apache.org gregory james marsh wrote: > > Hi Carl, > > A question from our group about the following client params you mentioned > in your email (included below): > > --max-frame-size N (65535) the maximum frame size to request. > --bounds-multiplier N (2) bound size of write queue (as a > multiple of > the max frame size). > --tcp-nodelay Turn on tcp-nodelay > > Could you further explain/clarify the behavior of "--bounds-multiplier". > We read over the code comments in > > trunk/qpid/cpp/src/qpid/client/ConnectionSettings.h It is used to determine how many messages/frames the producing thread in the application can get ahead of the IO layer. so 1 means lockstep, 2 is 2x etc... A low value will decrease the time that a message can 'age' in the buffer to be sent on the wire, but could hurt throughput, a large number can increase throughput but hurt latency (aging ).... The tuning of this number obviously is network setup dependent. Also, some basic server tuning can be done which depending on your gear should improve your numbers significantly. With fame size, rough guess is to set it ~ 100bytes larger than the message size you want to benchmark for low latency. regards Carl.