Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 67935 invoked from network); 11 Aug 2008 01:19:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Aug 2008 01:19:10 -0000 Received: (qmail 30499 invoked by uid 500); 11 Aug 2008 01:19:02 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 30468 invoked by uid 500); 11 Aug 2008 01:19:01 -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 30456 invoked by uid 99); 11 Aug 2008 01:19:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Aug 2008 18:19:01 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates 72.14.220.159 as permitted sender) Received: from [72.14.220.159] (HELO fg-out-1718.google.com) (72.14.220.159) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Aug 2008 01:18:05 +0000 Received: by fg-out-1718.google.com with SMTP id 22so855841fge.1 for ; Sun, 10 Aug 2008 18:18:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=hCWDqfdz+PJLucQq4a2B9jVufIso6xPf/gL8HIaPxPU=; b=IF4KyFtO/TX/hw60RadTSOodxwJxS46L1c4HwkVz/4xEI2yMEaSHUtFwdt9j+QVUDZ IFXIofE0yKZKAovL4qhggi6vTI3BRAkaRdjQ+7Mj2a5/yuVC6ALNoHZrjk664s02t8j2 WV+fTRhYmfaDtbPRrZK/v2C3ERmoSS8Fw+1As= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Y/HIneZq0XxYQX2wNu11XDSFOtyDnWr6JbqpsIvulhjiY2K9c9XhvaWQePRq6lYzCl TD+I3EAqToTqIaXRMczAJn7vc5WbwW4Kwg3dn0PBWIqtJv1zPaXFTltaKnC/hKxq+iGq tcSIHaZ+mgbd0beWg/nKtDb6VsKC99FqymMl4= Received: by 10.86.91.12 with SMTP id o12mr7051157fgb.1.1218417512472; Sun, 10 Aug 2008 18:18:32 -0700 (PDT) Received: by 10.86.57.13 with HTTP; Sun, 10 Aug 2008 18:18:32 -0700 (PDT) Message-ID: <25aac9fc0808101818k1af19b37u9b55535c66fc1164@mail.gmail.com> Date: Mon, 11 Aug 2008 02:18:32 +0100 From: sebb To: "JMeter Users List" Subject: Re: Remote servers and ramp up In-Reply-To: <114417750808010233y29f7a90em231b8a4baf1ab9df@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2AB2B3C160BFC14CB0D94D437513C3BA0169400F@revmail02.revenuedomain.ie> <114417750808010233y29f7a90em231b8a4baf1ab9df@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org See also: http://jakarta.apache.org/jmeter/usermanual/best-practices.html#beanshell_server On 01/08/2008, Andrey Beznogov wrote: > Hi, > > trying to synchronize the request generation by different servers is > probably too hard to implement. > > It is easier - and probably more realistic if we think about user > generated requests - to just insert a (Once Only Controller - Uniform > Random Timer) as the first element of your tests ThreadGroup. > > If you set Random Delay Maximum to (RampUpTime/NumberOfThreads), and > Constant Delay Offset to 0, threads spawned by each server will be > randomly paused at the beginning, and the requests generated by the > first Sampler on each server will be uniformly distributed in time. > > Regards, > Andrey > > > On Fri, Aug 1, 2008 at 12:41 PM, Fitzpatrick, Adrian wrote: > > > > 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. > > > > 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. > > > > 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 > > > > > > > > > -- > diem perdidi > > > --------------------------------------------------------------------- > 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