Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 36517 invoked from network); 30 Jun 2010 10:53:36 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Jun 2010 10:53:36 -0000 Received: (qmail 81351 invoked by uid 500); 30 Jun 2010 10:53:35 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 81136 invoked by uid 500); 30 Jun 2010 10:53:33 -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 81128 invoked by uid 99); 30 Jun 2010 10:53:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jun 2010 10:53:32 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jehanzeb.qayyum@gmail.com designates 209.85.216.44 as permitted sender) Received: from [209.85.216.44] (HELO mail-qw0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jun 2010 10:53:24 +0000 Received: by qwe5 with SMTP id 5so283106qwe.31 for ; Wed, 30 Jun 2010 03:52:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=8MH2eEfg5kOQizh2wgfEVKze7HJRzilZ4tks1aVOW+0=; b=VzAEeAOxyvSnsd8cn64KF7DKpvnTngGQ9vL57WQII8NYgX253f1DUcpxe9Oii1fiFC 2sYIEbLqYI23altsZOAnGUNRPj38BkQ54ydTjhqJ3D1l3XJjPhVGu4VMsc3e5XbX25ZF VHm9QsK6IYMS3bFy1s5NM3nbbN+vw42rtIx7o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=LfCjiM/YwaJluU2g0L+f+GLBVn4H1cN83WZeF9QXa9wzsdSkZ94Toa2SLzAZc925x4 eBjpSZ2J4Q9tnctwwwDyNwZrdFy+WDXJvafw4/1JFrKmmIa9EgOVu73y26AS0FjjkjXP rDxKoreBURH/5vru2wAaGte5XYxbhyXKp3i04= Received: by 10.224.72.6 with SMTP id k6mr5993194qaj.110.1277895134303; Wed, 30 Jun 2010 03:52:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.11.80 with HTTP; Wed, 30 Jun 2010 03:51:54 -0700 (PDT) In-Reply-To: References: <1497298471-1277877167-cardhu_decombobulator_blackberry.rim.net-297129890-@bda2253.bisx.produk.on.blackberry> <318126678-1277892486-cardhu_decombobulator_blackberry.rim.net-1618933466-@bda2253.bisx.produk.on.blackberry> From: jz Date: Wed, 30 Jun 2010 15:51:54 +0500 Message-ID: Subject: Re: JMetere JDBC Test Confusing Result To: JMeter Users List Content-Type: multipart/alternative; boundary=00c09fa21e318a5876048a3d2528 X-Virus-Checked: Checked by ClamAV on apache.org --00c09fa21e318a5876048a3d2528 Content-Type: text/plain; charset=ISO-8859-1 This is exactly what i did. I wanted to open all 10 connections before i do actual testing. For this i added Thread Group 1 with 10 threads and a dummy select statement. Now thread group 2 which has 100 threads, starts with a delay of 5 seconds. In those 5 seconds Thread Group 1 has opened all connections and thread group 2 uses those opened connections only. Regards, Jehanzeb Qayyum On Wed, Jun 30, 2010 at 3:45 PM, sebb wrote: > On 30/06/2010, sebb wrote: > > On 30/06/2010, jz wrote: > > > > > Guys its a web applications. And connection pooling will be provided by > > > container. I wanted to test only the time taken by query/stored > procedure, > > > not the time of spent in opening connection. > > > > > > So don't use connection pooling in JMeter. > > > > If you think about it, there will still be the same number of > > connections generated. > > > > Either 10 in a pool, or 1 each in 10 threads. > > > > Also, the connections are opened before the samplers run anyway. > > Actually, I'm not sure that is true; it's possible that the connection > is opened on first use. > > In which case, just add a dummy select statement at the start of the test. > > Note that this may or may not work if you are using connection > pooling, because the first samples in each thread may share a > connection. In which case the first use (and connection open) may > occur in the middle of testing. > > For repeatability, don't use pooling. > > > > > > Regards, > > > Jehanzeb Qayyum > > > > > > > > > > > > > > > > > > On Wed, Jun 30, 2010 at 3:19 PM, sebb wrote: > > > > > > > On 30/06/2010, Sudip Kumar Bhattacharya < > skb.subscriptions@gmail.com> > > > > wrote: > > > > > If it is a j2ee web application, app server wud be doing the > connection > > > > pooling. > > > > > > > > Yes, agreed. > > > > > > > > > If it is a desktop app running from multiple terminals then > connection > > > > pooling won't be there across multiple users. > > > > > > > > Yes, agreed. > > > > > > > > > I hope you are testing for a web application. > > > > > > > > If the OP wants to emulate the behaviour of a web application, then > > > > they need to test using the pooling code actually used by the > > > > applicaton, not the pooling code which happens to be used by > JMeter. > > > > > > > > Note that the JMeter pooling implementation cannot be changed > (except > > > > by rewriting the code!). > > > > > > > > Alternatively, work out how many independent connections are > created > > > > by the web application, and use that many JMeter threads. > > > > > > > > > > > > --------------------------------------------------------------------- > > > > 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 > > --00c09fa21e318a5876048a3d2528--