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 91906917B for ; Thu, 16 Feb 2012 19:59:16 +0000 (UTC) Received: (qmail 28371 invoked by uid 500); 16 Feb 2012 19:59:15 -0000 Delivered-To: apmail-jmeter-user-archive@jmeter.apache.org Received: (qmail 28324 invoked by uid 500); 16 Feb 2012 19:59:15 -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 28313 invoked by uid 99); 16 Feb 2012 19:59:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Feb 2012 19:59:15 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shettyd@gmail.com designates 209.85.214.171 as permitted sender) Received: from [209.85.214.171] (HELO mail-tul01m020-f171.google.com) (209.85.214.171) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Feb 2012 19:59:09 +0000 Received: by obcuy19 with SMTP id uy19so4450151obc.2 for ; Thu, 16 Feb 2012 11:58:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=z1T4Q4Y0J9FLtm5lR/8mPxDfJ/rtxRtJI7s39OhHjL8=; b=M3pgJPk0AqIhgme8EcWjPZK+YbV3ZpnDH8R2WuWFFZxTjxbknac0OQNsn8OO+Bl/pX pSZZhntDWDJQer/nwUzWl0dC7Y44LRQMk1SuyEdwvBx9AWRyXq73rhndh2++Mu8Ptrj2 Lt+TrsgzwNMEOBFiIOPJxXV9BpRcPKyg3show= MIME-Version: 1.0 Received: by 10.182.72.35 with SMTP id a3mr2942773obv.16.1329422329005; Thu, 16 Feb 2012 11:58:49 -0800 (PST) Received: by 10.182.72.197 with HTTP; Thu, 16 Feb 2012 11:58:48 -0800 (PST) In-Reply-To: References: Date: Thu, 16 Feb 2012 11:58:48 -0800 Message-ID: Subject: Re: Progressively adding "users" From: Deepak Shetty To: JMeter Users List Content-Type: multipart/alternative; boundary=f46d04463270ad44aa04b91a418d --f46d04463270ad44aa04b91a418d Content-Type: text/plain; charset=ISO-8859-1 Option 1 http://code.google.com/p/jmeter-plugins/ has some thread groups that do what you want(easiest) If using JMeter byitself then you have some options a. Multiple thread groups that start at scheduled times b. Create the number of threads in a threadgroup as a property. Invoke Jmeter using ant or something with different values c. Use Ramp up time creatively along with sync timers. On Thu, Feb 16, 2012 at 9:25 AM, James Carr wrote: > As part of some database benchmarking my team has been trying to do to > help determine capacity I've been using Jmeter's JDBC Sampler and a Summary > Report listener to try and gauge at what point we'll begin to see an upward > curve in what a single node database can handle. > > So far our process has gone like this: > > 1. Run with ten threads, 10 max connections, for 240 seconds > > 2. Record results in excel > > 3. Repeat step three until we reach 100 concurrent connections > > 4. Plot graph from results > > > My questions is... is this the "right way" to do this, or will I be > getting dubious results? Also, is there some way to automate this setup > rather than changing the numbers and running 10 times? > > > Thanks, > James > > --f46d04463270ad44aa04b91a418d--