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 7029F6BF1 for ; Fri, 20 May 2011 19:02:31 +0000 (UTC) Received: (qmail 22719 invoked by uid 500); 20 May 2011 19:02:30 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 22698 invoked by uid 500); 20 May 2011 19:02:30 -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 22689 invoked by uid 99); 20 May 2011 19:02:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 May 2011 19:02:30 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 May 2011 19:02:25 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QNUxY-0006d6-Gz for jmeter-user@jakarta.apache.org; Fri, 20 May 2011 12:02:04 -0700 Date: Fri, 20 May 2011 12:02:04 -0700 (PDT) From: zillakilla To: jmeter-user@jakarta.apache.org Message-ID: <1305918124494-4413339.post@n5.nabble.com> In-Reply-To: References: Subject: Re: Timers, Think Time between requests, and Best Practices MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I think there are many ways of doing what you need but, 1 simple way is to use a ConstantThroughputTimer instead of the GaussianRandomTimer This can assist with think time and also to calculate number of users Knowing what the expected throughput vs actual throughput is also a useful metric example: with 1 thread running, set the ConstantThroughputTimer to 60 reqs per min (60 being: number of threads * 60 = 1 req per sec per thread) So.... 1 thread = 1 req per sec if you have a think time of say 6 secs... then 1 thread with a CTP of 60 = 10 users (or a think time of 4 secs ... then 1 thread = think time / 60 = 15 users) If you did not get close to a total throughput of 60 reqs per min (1 req per sec) then you know you have problems If i wanted to simulate 300 users using this logic (with think time = 6 secs), i would have 5 threads running in 1 thread group with the ConstantThroughputTimer set to 300 (300 being: number of threads * 60 = 1 req per sec per thread) Did it make sense? HTH zilla -- View this message in context: http://jmeter.512774.n5.nabble.com/Timers-Think-Time-between-requests-and-Best-Practices-tp4410057p4413339.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