Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 46287 invoked from network); 12 Nov 2007 07:44:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Nov 2007 07:44:41 -0000 Received: (qmail 90241 invoked by uid 500); 12 Nov 2007 07:44:23 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 90219 invoked by uid 500); 12 Nov 2007 07:44:23 -0000 Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "JMeter Users List" Reply-To: "JMeter Users List" Delivered-To: mailing list jmeter-user@jakarta.apache.org Received: (qmail 90207 invoked by uid 99); 12 Nov 2007 07:44:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Nov 2007 23:44:23 -0800 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [216.82.254.19] (HELO mail96.messagelabs.com) (216.82.254.19) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 12 Nov 2007 07:45:07 +0000 X-VirusChecked: Checked X-Env-Sender: sonam.chauhan@ce.com.au X-Msg-Ref: server-4.tower-96.messagelabs.com!1194853438!10530328!1 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- X-Originating-IP: [203.23.60.182] Received: (qmail 21020 invoked from network); 12 Nov 2007 07:43:58 -0000 Received: from unknown (HELO mx.ce.com.au) (203.23.60.182) by server-4.tower-96.messagelabs.com with SMTP; 12 Nov 2007 07:43:58 -0000 Received: from syd1exc01.CE.CORP (syd1exc01.ce.corp [10.20.22.83]) by mx.ce.com.au (Postfix) with ESMTP id 050826407D for ; Mon, 12 Nov 2007 18:43:45 +1100 (EST) Received: from syd1exc04.CE.CORP ([10.20.22.169]) by syd1exc01.CE.CORP with Microsoft SMTPSVC(6.0.3790.3959); Mon, 12 Nov 2007 18:43:44 +1100 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: 'Spread' for distributed testing Date: Mon, 12 Nov 2007 18:43:44 +1100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 'Spread' for distributed testing Thread-Index: AcgiD2kklRxWf2hwQ/CeHMixQeXKBAAWDE8w From: "Sonam Chauhan" To: "JMeter Users List" X-OriginalArrivalTime: 12 Nov 2007 07:43:44.0877 (UTC) FILETIME=[C0BA89D0:01C824FF] X-Virus-Checked: Checked by ClamAV on apache.org Sebb:=20 > It's mainly a problem because of the data volumes that are required. I > don't see how changing the transport mechanism can change that. I thought Spread had bandwidth throttling features so that logs entries could queue up and stream in a bandwidth limited manner to the end destination - however Spread may not have these features. A workaround would be to setup virtual network interfaces limited to, say, 10 Mbps and have the Spread components bind to those interfaces, but that may be too much work. In any case, I've asked the question on the Spread user list.=20 > > Is it possible to prototype this idea using a BeanShell listener? > > > I think it would be difficult. > > Listeners are handled specially in client-server mode. Thanks. Kind regards, Sonam Chauhan --=20 Corporate Express Australia Ltd.=20 Phone: +61-2-93350725, Email: sonam.chauhan@ce.com.au -----Original Message----- From: sebb [mailto:sebbaz@gmail.com]=20 Sent: Friday, 9 November 2007 12:57 AM To: JMeter Users List Subject: Re: 'Spread' for distributed testing In 08/11/2007, Sonam Chauhan wrote: > Just a thought - Would the 'Spread Toolkit' (http://www.spread.org/) be > useful in JMeter distributed testing? > > > > From the Spread website: > > Spread functions as a unified message bus for distributed applications, > and provides highly tuned application-level multicast, group > communication, and point to point support. > > > > From what I understand, an existing problem in JMeter distributed > testing is collating logs back to the master server, particularly when > the logs capture extra information (e.g., the HTTP response). Perhaps > using Spread could help in this? It has a Java API encapsulated in one > package. > It's mainly a problem because of the data volumes that are required. I don't see how changing the transport mechanism can change that. > > Is it possible to prototype this idea using a BeanShell listener? > I think it would be difficult. Listeners are handled specially in client-server mode. > > Kind regards, Thanks anyway. > Sonam Chauhan > > -- > > Corporate Express Australia Ltd. > > Phone: +61-2-93350725, Email: sonam.chauhan@ce.com.au > > > > Spread Toolkit > > http://www.spread.org/ > > > > Java Interface to the Spread Toolkit > > http://www.spread.org/docs/javadocs/java.html > > > > An interesting article on using Spread to unify apache access logs. > > http://www.samag.com/documents/s=3D7789/sam0302a/0302a.htm > > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org