Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 60260 invoked from network); 21 Jan 2009 15:39:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Jan 2009 15:39:48 -0000 Received: (qmail 46337 invoked by uid 500); 21 Jan 2009 15:39:47 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 45798 invoked by uid 500); 21 Jan 2009 15:39:45 -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 45786 invoked by uid 99); 21 Jan 2009 15:39:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2009 07:39:45 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2009 15:39:36 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LPfAh-0003Zi-Nu for jmeter-user@jakarta.apache.org; Wed, 21 Jan 2009 07:39:15 -0800 Message-ID: <21585628.post@talk.nabble.com> Date: Wed, 21 Jan 2009 07:39:15 -0800 (PST) From: Pieter P To: jmeter-user@jakarta.apache.org Subject: Limit concurrent number of threads using Constant Throughput Timer? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: pieter@porthome.nl X-Virus-Checked: Checked by ClamAV on apache.org Hello, I'm using JMeter 2.3.2 to functionally test my web server. I have defined one Thread Group that uses a .CSV file to execute 3000 different test cases. Each test case sends an XML file over HTTPS (using a sampler) and parses the response. Some test cases take 90 seconds to execute by the webserver, and some test cases only 0.5 seconds. The problem is that the web server starts malfunctioning if it handles more than 50 concurrent transactions. The number 50 is configured, but cannot be changed because of other requirements. I have set the number of Threads to 3000 and the ramp up period to 3000 seconds. Since some test cases require 90 seconds to execute, more than 50 transactions will be executed concurrently at some time, causing the web server to malfunction. What I would like to achieve is to limit the amount of concurrent HTTPS connections to my webserver. I have read that the Constant Throughput Timer can be used to create time-waits based on other variables than transaction-throughput, for example based in the amount of currently running threads. I could not figure out how to implement this, though.. Is it possible to limit the amount of concurrent HTTPS connections using a Constant Throughput Timer in the Thread Group? Do different solutions exists? -- View this message in context: http://www.nabble.com/Limit-concurrent-number-of-threads-using-Constant-Throughput-Timer--tp21585628p21585628.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