Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 55673 invoked from network); 12 Dec 2008 13:05:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Dec 2008 13:05:51 -0000 Received: (qmail 41193 invoked by uid 500); 12 Dec 2008 13:06:01 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 41178 invoked by uid 500); 12 Dec 2008 13:06: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 41166 invoked by uid 99); 12 Dec 2008 13:06:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2008 05:06:01 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [194.0.215.2] (HELO oslproxyp1.tandberg.com) (194.0.215.2) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2008 13:05:40 +0000 Received: from OSLEXCP11.eu.tandberg.int ([10.47.136.43]) by oslproxyp1.tandberg.com (8.13.1/8.13.1) with ESMTP id mBCD5IFR013446 for ; Fri, 12 Dec 2008 14:05:18 +0100 Received: from oslexcp4.eu.tandberg.int ([10.47.136.108]) by OSLEXCP11.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Dec 2008 14:05:18 +0100 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: passing Number of threads from command prompt Date: Fri, 12 Dec 2008 08:05:14 -0500 Message-ID: <4C18B43DBBF99443A65145AE575757EF63B0D7@oslexcp4.eu.tandberg.int> In-Reply-To: <20970476.post@talk.nabble.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: passing Number of threads from command prompt Thread-Index: AclcIYPTl2BYiYihQiuqOUmeJ7vqQwAODLig References: <20952721.post@talk.nabble.com> <25aac9fc0812110637r36a271ceu4e755abbd5f3f853@mail.gmail.com> <20970476.post@talk.nabble.com> From: "Steve Kapinos" To: "JMeter Users List" X-OriginalArrivalTime: 12 Dec 2008 13:05:18.0877 (UTC) FILETIME=[486E4CD0:01C95C5A] X-Scanned-By: MIMEDefang 2.65 on 194.0.215.2 X-Virus-Checked: Checked by ClamAV on apache.org In the test plan, in the thread group settings, populate those fields with functions that evaluate a property. So you make up a bunch of parameters, something like pThreadGroup1 pThreadGroup1ramp pThreadGroup2 pThreadGroup2ramp ... Etc In the test plan itself, define the number of users for ThreadGroup1 to be a function that evaluates the property ${__P(pThreadGroup1)} And the rampup to be ${__P(pThreadGroup1ramp)} Then when you run the test plan, pass the values to use for the properties.. either via a properties file or via command line switches Jmeter -t testplan.jmx -JpThreadGroup1=3D10 Etc -Steve -----Original Message----- From: Krishnakanth [mailto:krishnakanth.pps@gmail.com]=20 Sent: Friday, December 12, 2008 1:18 AM To: jmeter-user@jakarta.apache.org Subject: Re: passing Number of threads from command prompt Hi Sebb. Could you get a little deeper. Where should I find this file.=20 probably a 2-3 steps would be awesome from your part. Pleaseee.. thanks. Krishnakanth sebb-2-2 wrote: >=20 > 2008/12/11 Krishnakanth : >> >> If there are few thread groups in a Jmeter test plan and if we want to >> pass >> the number of threads (users), >> Ramp up time as parameters from command prompt in the below mentioned >> way. >> Does this work? >> >> To specify 1 user per user group for 5 groups (total 5 users), ramp up in >> 1 >> second, >> and 25 loops each group iterates over the same operation set: >> >> ./bin/jmeter.lucene -t MyWebPerfScenario.jmx \\ >> -Jgroup1.threads=3D1 -Jgroup1.loops=3D25 -Jgroup1.rampup=3D1 \\ >> -Jgroup2.threads=3D1 -Jgroup2.loops=3D25 -Jgroup2.rampup=3D1 \\ >> -Jgroup3.threads=3D1 -Jgroup3.loops=3D25 -Jgroup3.rampup=3D1 \\ >> -Jgroup4.threads=3D1 -Jgroup4.loops=3D25 -Jgroup4.rampup=3D1 \\ >> -Jgroup5.threads=3D1 -Jgroup5.loops=3D25 -Jgroup5.rampup=3D1 >> I tried it, but its not taking the parameters. Do we have to make some >> changes in the Jmeter.properties file to do so? >> >=20 > No, but you do need to refer to the properties in the appropriate > thread group GUI fields. >=20 > For example, in the Ramp-up field, use ${__P(group1.rampup)} etc. >=20 >=20 >> -- >> View this message in context: >> http://www.nabble.com/passing-Number-of-threads-from-command-prompt-tp20 952721p20952721.html >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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 >=20 >=20 >=20 --=20 View this message in context: http://www.nabble.com/passing-Number-of-threads-from-command-prompt-tp20 952721p20970476.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- 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