Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 25665 invoked from network); 1 Aug 2008 08:42:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Aug 2008 08:42:16 -0000 Received: (qmail 58585 invoked by uid 500); 1 Aug 2008 08:42:09 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 58562 invoked by uid 500); 1 Aug 2008 08:42:09 -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 58551 invoked by uid 99); 1 Aug 2008 08:42:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Aug 2008 01:42:09 -0700 X-ASF-Spam-Status: No, hits=-1.4 required=10.0 tests=RCVD_IN_DNSWL_MED,RCVD_NUMERIC_HELO,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [137.191.227.44] (HELO prim-smtp-2.revenue.ie) (137.191.227.44) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 01 Aug 2008 08:41:13 +0000 Received: from localhost (localhost [127.0.0.1]) by prim-smtp-2.revenue.ie (Postfix) with ESMTP id DF18D50242F for ; Fri, 1 Aug 2008 09:41:37 +0100 (IST) X-Virus-Scanned: by Copperfasten Mail Firewall at revenue.ie Received: from revjnrdcont03 (unknown [25.4.1.90]) by prim-smtp-2.revenue.ie (Postfix) with ESMTP id 7A16F502427 for ; Fri, 1 Aug 2008 09:41:37 +0100 (IST) Received: from 25.3.1.211 ([25.3.1.211]) by localhost (PostX Enterprise 5.3.1 SMTP Adapter) with SMTP ID 105 for ; Fri, 1 Aug 2008 09:41:38 +0100 (BST) Received: from REVMAIL02.RevenueDomain.ie ([25.34.1.72]) by savgw2.revenuedomain.ie (SMSSMTP 4.1.11.41) with SMTP id M2008080109413725989 for ; Fri, 01 Aug 2008 09:41:37 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Subject: Remote servers and ramp up Date: Fri, 1 Aug 2008 09:41:36 +0100 Message-ID: <2AB2B3C160BFC14CB0D94D437513C3BA0169400F@revmail02.revenuedomain.ie> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Is there anything running every minute in jmeter? Thread-Index: Acjy8YbFo8rmYYNWSSSA1ShdoEX6xAAvQLYQ From: "Fitzpatrick, Adrian" To: "JMeter Users List" X-Virus-Checked: Checked by ClamAV on apache.org Hi all, Our JMeter testing platform consists of 7 PCs - one controller and 6= running Jmeter servers that we use for load generation. Many of the tests we run= are stress tests - where we gradually increase the load over time to establish system capacity and breaking points. We use the JMeter "Ramp-Up Period" setting to give this testing profile. This works fine when only running on= a single PC, however, we have issues running these types of tests spread= across our remote PCs.=20 For example if we want to run a test with 60 threads, we have a thread= group with 10 threads on our controller, and then start the test running remotely on the six load generators. In this scenario, if we use a ramp up, the load is increased in steps of 6 threads, rather than gradually 1 thread at a= time as we would like.=20 Can anyone suggest any way for use to get round this issue while still= using remote JMeter servers? Perhaps this is changed in a new version? We are currently using 2.3RC4 and I've reviewed the release notes for later= versions but haven't seen anything. Any suggestions would be welcomed! Regards, Adrian ************************ This message has been delivered to the Internet by the Revenue Internet= e-mail service (OP) ************************* --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org