Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 41574 invoked from network); 8 Aug 2005 17:45:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Aug 2005 17:45:39 -0000 Received: (qmail 16629 invoked by uid 500); 8 Aug 2005 17:45:36 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 16600 invoked by uid 500); 8 Aug 2005 17:45:36 -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 16586 invoked by uid 99); 8 Aug 2005 17:45:36 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2005 10:45:36 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of sebbaz@gmail.com designates 64.233.182.207 as permitted sender) Received: from [64.233.182.207] (HELO nproxy.gmail.com) (64.233.182.207) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2005 10:45:58 -0700 Received: by nproxy.gmail.com with SMTP id c2so238751nfe for ; Mon, 08 Aug 2005 10:45:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bL426M6A1MPyPVyLThshPBxpzjy+ok02w9y8dm/VezA04pHmWtAPOSxICPLtxyyQnciaDYNCDh6RUQ2+BfoulukDHwz4ZWjj+Xk46/cqNOqNLyMnB04j0UAknaTThLIrOnZUkjRmlRb3Y4kIBmgVZsKiKRflvQKJu/KgFHekaJw= Received: by 10.48.43.14 with SMTP id q14mr45514nfq; Mon, 08 Aug 2005 10:45:30 -0700 (PDT) Received: by 10.48.144.17 with HTTP; Mon, 8 Aug 2005 10:45:30 -0700 (PDT) Message-ID: <25aac9fc050808104534bac596@mail.gmail.com> Date: Mon, 8 Aug 2005 18:45:30 +0100 From: sebb To: JMeter Users List Subject: Re: Switch Controller Problem In-Reply-To: <6134F668515B04409948FBEB644A3E0D34384F@msmail.textwise.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <6134F668515B04409948FBEB644A3E0D34384F@msmail.textwise.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This could perhaps be a problem with the retrieval of the switch value, rather than the controller per se. Might be worth wrapping the value in a log() function call to check it. Otherwise, it might be a bug, in which case please create a Bugzilla issue with a short test case (the Java Sampler is useful here). S. On 07/08/05, Jeremy Dahlgren wrote: > Below is a posting where I asked about the Constant Throughput Timer. Th= e posting describes my test plan and use of a Switch Controller. I am seei= ng weird behavior where the switch is executing the wrong sampler at times.= My first impression is that there is an issue with the user parameters ge= tting updated while another thread is in the switch controller. In the tes= t I had 16 threads executing within a thread group where the switch control= ler is located. I was curious as to whether anyone else has had problems u= sing the switch controller. It is much faster than the if statement contro= llers i was using before to determine the right sampler to run and would li= ke to stay with the switch. Any ideas? >=20 > Thanks, >=20 > Jeremy >=20 > > -----Original Message----- > > From: Jeremy Dahlgren > > Sent: Sunday, August 07, 2005 5:22 PM > > To: 'jmeter-user@jakarta.apache.org' > > Subject: Constant Throughput Timer Troubles > > > > I have a test that needs to spread 1285200 requests across > > 3.5 hours. The same test also needs to spread 25200 requests > > of a different category across the same 3.5 hours. My test > > plan has two thread groups. In each thread group there is a > > user parameters that reads requests from a file. The file > > has an integer that determines the request type and then the > > request parameters. After the user parameters there are > > constant throughput timers and a switch controller holding > > the samplers. The constant throughput timers use properties > > passed in from the command line. The first gets 1285200 / > > 210 =3D 6120 samples per minute and the second gets 25200 / 210 > > =3D 120 samples per minute. The problem is that the test > > completes in 2 hours and 20 minutes. I was under the > > impression that the constant throughput timer throttles the > > samples executed "within the container where you put the > > timer" which in my test is the thread group. Is there a > > problem with the construction of my test plan? I'm not sure > > why the requests aren't being spread evenly across the 3.5 > > hours. Any help would be greatly appreciated. > > > > Thanks, > > > > Jeremy > > > > > > thread group 0 > > -- user parameters > > -- constant throughput timer > > -- switch controller > > -- sampler 0 > > -- sampler 1 > > -- sampler 2 > > > > thread group 1 > > -- user parameters > > -- constant throughput timer > > -- switch controller > > -- sampler 0 > > -- sampler 1 > > -- sampler 2 > > -- sampler 3 > > -- sampler 4 > > -- sampler 5 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org >=20 > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org