Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 68246 invoked from network); 7 Oct 2009 22:07:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Oct 2009 22:07:19 -0000 Received: (qmail 42615 invoked by uid 500); 7 Oct 2009 22:07:19 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 42569 invoked by uid 500); 7 Oct 2009 22:07:19 -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 42559 invoked by uid 99); 7 Oct 2009 22:07:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2009 22:07:18 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates 209.85.219.208 as permitted sender) Received: from [209.85.219.208] (HELO mail-ew0-f208.google.com) (209.85.219.208) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2009 22:07:08 +0000 Received: by ewy4 with SMTP id 4so2345511ewy.37 for ; Wed, 07 Oct 2009 15:06:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=YlFOookW3UaPO4RbZX7kVtfFxJTdkSvJIrSOTgXnHg4=; b=Ktwf7e69bFmoC3JZdorSbi3dFvyaPIR/atMgIX8x/UfJDwAacO7Axc3JXH3XXpIgoW z5cmUo4ysfip1It/jvbPluqiwvmItOK8Z81dQp3ziwj4ZWG3tM/QNMk0k/ifmV+tw4AI IPD7TANYnQsls7GAJXP4X6f3kVw7pZkDz8AvA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=KOzBQYQK9Vmdn3IQxgrTABceQQ1M71IBwrqb9IYuYKPM6358Cn+PyVWorqn/PSs3sn SGxb5BSK/m5CII5DGqgpHVIPFJgVSdHiOF9mVzusqmxqO56XKynS7rxKra36HrRkX1fd DpsqSfBj9GhD4ejOz5V5SETi6/HFI9XGa3Xn4= MIME-Version: 1.0 Received: by 10.216.85.144 with SMTP id u16mr161712wee.3.1254953208027; Wed, 07 Oct 2009 15:06:48 -0700 (PDT) In-Reply-To: <25795202.post@talk.nabble.com> References: <25793044.post@talk.nabble.com> <25aac9fc0910071447i5074921ei89b689afe970c27b@mail.gmail.com> <25795202.post@talk.nabble.com> Date: Wed, 7 Oct 2009 23:06:48 +0100 Message-ID: <25aac9fc0910071506j2f56472fo9b82f822af4d2e45@mail.gmail.com> Subject: Re: Connection Pool Pre-Populating From: sebb To: JMeter Users List Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 07/10/2009, skatz wrote: > > I do want to use the connection pool (at least I think I do). If in doubt, don't ... > What I don't > want, is to have the time it takes to open a connection included in my test > results. > > Basically, the way it is right now, there will be some number of request > (equal to the number of connections that are supposed to be in the pool) for > which their response times include the time it took to create the > connection. Subsequent threads don't have this delay, rightly so, because > for them, the connection has already been created. > > So is there some way that one set of threads (not counted in the test) can > cause the connection pool to be populated, so that subsequent threads > (counted in the test) can benefit from it? Or some other way I can tell > JMeter to establish all the connections that are supposed to be in the pool > before the threads need them? > No. > > > > sebb-2-2 wrote: > > > > On 07/10/2009, skatz wrote: > >> > >> I'm running some test against MySQL and it seems that the first results > >> are > >> skewed by the time it takes to fill the connection pool w/ connections. > >> Is > >> there a way to pre-populate the connection pool. If not, what do people > >> usually do? Just drop first X results where X is the number of > >> connection > >> in the pool? > > > > Don't use a connection pool unless you want to test with pooled > > connections. > > Just set the max number of connections to 0 and pooling will be disabled. > > > >> thanks, > >> > >> skatz > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/Connection-Pool-Pre-Populating-tp25793044p25793044.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 > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org > > > > > > > > > -- > View this message in context: http://www.nabble.com/Connection-Pool-Pre-Populating-tp25793044p25795202.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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org