Return-Path: X-Original-To: apmail-jakarta-jmeter-user-archive@www.apache.org Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8669F9131 for ; Fri, 21 Oct 2011 16:15:26 +0000 (UTC) Received: (qmail 3488 invoked by uid 500); 21 Oct 2011 16:15:25 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 3459 invoked by uid 500); 21 Oct 2011 16:15:25 -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 3450 invoked by uid 99); 21 Oct 2011 16:15:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Oct 2011 16:15:25 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates 209.85.212.44 as permitted sender) Received: from [209.85.212.44] (HELO mail-vw0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Oct 2011 16:15:17 +0000 Received: by vws5 with SMTP id 5so3685318vws.31 for ; Fri, 21 Oct 2011 09:14:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=1URntYDPt/OOZLEQtEiReWp4Br8NMwbQXq69yvPdfmk=; b=Nif9Jdglp3VFchAW/SHh5MyevFLyhnD8ng8+4fnJrTbI/sYxVMyDc7E00GTPH0Wmjt 8u0WqDgITygzNZdNlKObC0gpoBJ2fm4InmSZepm/qzNXdiUwJ1Ft4sg5laOOmJroFQwj wFgPiEg+JNZ/UyRpMA3VDxjCifg6QfUyoTtIg= MIME-Version: 1.0 Received: by 10.52.114.232 with SMTP id jj8mr14736429vdb.94.1319213696724; Fri, 21 Oct 2011 09:14:56 -0700 (PDT) Received: by 10.220.185.201 with HTTP; Fri, 21 Oct 2011 09:14:56 -0700 (PDT) In-Reply-To: References: Date: Fri, 21 Oct 2011 17:14:56 +0100 Message-ID: Subject: Re: Constant Throughput Timer vs Throughput Shaping Timer (JMeter plugin)? From: sebb To: JMeter Users List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On 21 October 2011 15:56, Adrian Speteanu wrote: > The BS Server was a nice addition. If the Throughput timer is shared by a= ll > threads can you still change its value dynamically? Yes, as the page says, you can use the server to set a property (which is global to JMeter) and then reference the property in th CTT. The BSH server runs in its own thread - not sure it's possible to set JMeter variables (which are local to a thread). > Regards, > Adrian S > > On Fri, Oct 21, 2011 at 2:42 AM, sebb wrote: > >> On 21 October 2011 00:40, sebb wrote: >> > On 21 October 2011 00:36, David Luu wrote: >> >> Thanks, the beanshell server looks useful for what I'd want. >> > >> > That's very flexible but it would be simpler if the variable were set >> > in the test plan itself. >> > >> > e.g. if you wanted to ramp up gradually, you could use a counter with >> > a suitable increment to define the throughput variable. >> >> I meant to add: for experimental purposes, I suggest using a test plan >> with some Java samplers; you can then test without annoying the >> neighbours ;-). >> >> >> On Thu, Oct 20, 2011 at 10:43 AM, sebb wrote: >> >> >> >>> On 20 October 2011 18:14, Adrian Speteanu wrot= e: >> >>> > Hey David, >> >>> > >> >>> > I've used both. >> >>> > >> >>> > Its not much to compare :). If you understand the Constant Through= put >> >>> Timer, >> >>> > then you understand both and it's easy to see that its major >> limitation >> >>> is >> >>> > that it holds (if possible) the throughput constant at the value y= ou >> >>> define >> >>> > (which was the intent). However if you want to easily create a mor= e >> >>> complex >> >>> > test scenario like: >> >>> >> >>> The "constant" can also be varied. If the constant is expressed as a >> >>> variable or function reference, that allows the throughput to be >> >>> varied at will. >> >>> >> >>> See for example: >> >>> >> >>> >> >>> >> http://jakarta.apache.org/jmeter/usermanual/best-practices.html#beanshel= l_server >> >>> >> >>> >> >>> > =A01. run a test with throughput 100 for 2 min >> >>> > =A02. continue for 2 more minutes with throughput 200 >> >>> > =A03. continue for 2 more minutes with throughput 500 >> >>> > to see how the application responds to these changes in the load >> >>> received, >> >>> > without the plugin you had to use more thread groups and configure >> the >> >>> > scheduling so you get the same effect. The plugin makes these use >> cases >> >>> > simple and more easy to understand. >> >>> > >> >>> > You can make things a lot more complicated than that if you'd like >> using >> >>> > both methods and a lot of imagination. >> >>> > >> >>> > On Tue, Oct 11, 2011 at 5:19 AM, David Luu >> wrote: >> >>> > >> >>> >> I was wondering if anybody has used both, and wonder how they >> compare. >> >>> >> Pros/cons of each. >> >>> >> >> >>> >> And how one could best simulate the Throughput Shaping Timer with >> the >> >>> >> constant throughput timer via variable/property that defines the >> >>> throughput >> >>> >> and changing it during test run. Particularly how would you >> implement >> >>> the >> >>> >> changing of the throughput variable and where to place in test pl= an. >> >>> >> >> >>> >> FYI, I'm refering to this JMeter plugin: >> >>> >> >> >>> >> http://code.google.com/p/jmeter-plugins/wiki/ThroughputShapingTim= er >> >>> >> >> >>> > >> >>> >> >>> --------------------------------------------------------------------= - >> >>> 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 >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org