Return-Path: X-Original-To: apmail-jmeter-user-archive@www.apache.org Delivered-To: apmail-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 7FC029B6A for ; Mon, 12 Mar 2012 11:32:39 +0000 (UTC) Received: (qmail 8922 invoked by uid 500); 12 Mar 2012 11:32:38 -0000 Delivered-To: apmail-jmeter-user-archive@jmeter.apache.org Received: (qmail 8878 invoked by uid 500); 12 Mar 2012 11:32:38 -0000 Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "JMeter Users List" Delivered-To: mailing list user@jmeter.apache.org Received: (qmail 8868 invoked by uid 99); 12 Mar 2012 11:32:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Mar 2012 11:32:38 +0000 X-ASF-Spam-Status: No, hits=3.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of marcelojara@hotmail.com designates 65.54.190.101 as permitted sender) Received: from [65.54.190.101] (HELO bay0-omc2-s26.bay0.hotmail.com) (65.54.190.101) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Mar 2012 11:32:32 +0000 Received: from BAY153-W43 ([65.54.190.125]) by bay0-omc2-s26.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 12 Mar 2012 04:32:11 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_b44a90e5-32d3-4966-aa53-86b7f776357b_" X-Originating-IP: [68.36.4.107] From: Marcelo Jara To: Subject: RE: Constant Throughput Timer and test duration conflict Date: Mon, 12 Mar 2012 07:32:11 -0400 Importance: Normal In-Reply-To: <1331449074375-5554206.post@n5.nabble.com> References: <1330777049772-5533559.post@n5.nabble.com> <1330966593168-5538131.post@n5.nabble.com> <1331337038667-5551974.post@n5.nabble.com> <1331371972950-5552613.post@n5.nabble.com> <1331444879391-5554159.post@n5.nabble.com>,<1331449074375-5554206.post@n5.nabble.com> MIME-Version: 1.0 X-OriginalArrivalTime: 12 Mar 2012 11:32:11.0858 (UTC) FILETIME=[C43A5B20:01CD0043] X-Virus-Checked: Checked by ClamAV on apache.org --_b44a90e5-32d3-4966-aa53-86b7f776357b_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Well=2C iteration count is only used for debugging or when creating new sam= plers only. I would gladly share my test plan with you if you want to look = at it. I already posted the requirements for the test. This system has over= a dozen consumers and exposes over 120 services. So each service must be h= it independently which is why a separate thread group is needed for each sa= mpler. This is my first jmeter test plan and I don't doubt that I may be d= oing something fundamentally wrong.=20 > Date: Sat=2C 10 Mar 2012 22:57:54 -0800 > From: apc@apc.kg > To: jmeter-user@jakarta.apache.org > Subject: Re: Constant Throughput Timer and test duration conflict >=20 > If you operate with fixed test duration=2C then iteration count makes no = sense=2C > because the same test duration may include different iterations=2C depend= ing > on server response time. > Well=2C all I hear about your case tells me that there's something may be > inefficient in your approach. > Maybe you should choose stress-test mode as your primary performance > criteria. Just my opinion. >=20 > ----- > -- > Andrey Pohilko > JP@GC Maintainer > -- > View this message in context: http://jmeter.512774.n5.nabble.com/Constant= -Throughput-Timer-and-test-duration-conflict-tp5533559p5554206.html > Sent from the JMeter - User mailing list archive at Nabble.com. >=20 > --------------------------------------------------------------------- > To unsubscribe=2C e-mail: user-unsubscribe@jmeter.apache.org > For additional commands=2C e-mail: user-help@jmeter.apache.org >=20 = --_b44a90e5-32d3-4966-aa53-86b7f776357b_--