Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 53060 invoked from network); 4 Jun 2009 04:34:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Jun 2009 04:34:36 -0000 Received: (qmail 10829 invoked by uid 500); 4 Jun 2009 04:34:48 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 10766 invoked by uid 500); 4 Jun 2009 04:34:47 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 10758 invoked by uid 99); 4 Jun 2009 04:34:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jun 2009 04:34:47 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of clinton.begin@gmail.com designates 209.85.221.191 as permitted sender) Received: from [209.85.221.191] (HELO mail-qy0-f191.google.com) (209.85.221.191) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jun 2009 04:34:39 +0000 Received: by qyk29 with SMTP id 29so809764qyk.4 for ; Wed, 03 Jun 2009 21:34:18 -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=rmoEFkGBqzWp833XBNSOcH4iOpJSmX9lAtxvQqaJ5Zw=; b=vbE5qhRXJlz/tkgIBSDexWXRxKwmQ91RG3PFexAKobtI9ItbIGogJen4ZR9Dq+piH4 gOdlCa4ujERSDZlyKBpSfdphKEK9OWcijD4KY4KSqF2Jpmeu72zRCkOsJwR7pZ/fm4E9 pLIRRUFfH0DvHyHYOGWTPTNC0f2wpjr1OlU7w= 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=ZX+Soj+Z/RtWXthS9NGEWXd4Q8tlfDr2ngBkdCH6TN04L7qJJvio412AyjxBxgM5vn wu5vbpZ+GaMVirK2CpnNwgJOjrb50tOy3FOuThbRVb4nX5T0LO61qAIzYKcuLWEooM/7 N1p4gBl+nyqDHtqpvu9OUpM6j9wIqTF8Sw4Rg= MIME-Version: 1.0 Received: by 10.220.91.133 with SMTP id n5mr1263384vcm.102.1244090058751; Wed, 03 Jun 2009 21:34:18 -0700 (PDT) In-Reply-To: <6892C825A8016D4681D01CF07391E45289F41C@PE-EVS.converge.com> References: <6892C825A8016D4681D01CF07391E45289F41C@PE-EVS.converge.com> Date: Wed, 3 Jun 2009 22:34:18 -0600 Message-ID: <16178eb10906032134y245c29c8s39e329e644026b6d@mail.gmail.com> Subject: Re: Connection Pooling From: Clinton Begin To: user-java@ibatis.apache.org Content-Type: multipart/alternative; boundary=0016e647622a0543b4046b7e4a24 X-Virus-Checked: Checked by ClamAV on apache.org --0016e647622a0543b4046b7e4a24 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit If you have a fast, well designed database with well written SQL, it's quite possible that you'd never need more than a few connections for many users. The default pool size for TopLink when I used it was 6 (4 read, 2 write or something like that). It's a common misconception that more connections == better performance. Clinton On Wed, Jun 3, 2009 at 12:35 PM, Vinaya Tirikkovalluru < vinaya.tirikkovalluru@converge.com> wrote: > Hi, > > > > I am using Ibatis+Jboss4.2.2 > > > > I have not configured connection pooling in Jboss. > > Ibatis takes care of everything. But I see a connection in the database > which is open in the morning but still being used, like reused. I just see a > couple of them and not too many. > > How could just the 2/3 connections serve all the concurrent users? Would it > be a good idea to have connection pooling set up? > > Please advice > > > > Vinaya > > > > > > ------------------------------ > This electronic message is intended only for the use of the individual(s) > or entity(ies) named above and may contain information which is privileged > and/or confidential. If you are not the intended recipient, be aware that > any disclosure, copying, distribution, dissemination or use of the contents > of this message is prohibited. If you received this message in error, please > notify the sender immediately. > --0016e647622a0543b4046b7e4a24 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If you have a fast, well designed database with well written SQL, it's = quite possible that you'd never need more than a few connections for ma= ny users.

The default pool size for TopLink when I used it was 6 (4 = read, 2 write or something like that).=A0 It's a common misconception t= hat more connections =3D=3D better performance.

Clinton

On Wed, Jun 3, 2009 at 12:35 = PM, Vinaya Tirikkovalluru <vinaya.tirikkovalluru@converge.com> wrote:

Hi,

=A0

I am using Ibatis+Jboss4.2.2

=A0

I have not configured connection pooling in Jboss.

Ibatis takes care of everything. But I see a connection in the database which is open in the morning but still being used, like reused. I = just see a couple of them and not too many.

How could just the 2/3 connections serve all the concurrent users? Would it be a good idea to have connection pooling set up?

Please advice

=A0

Vinaya

=A0

=A0

This electronic message is intended only for the use of the individual(s) o= r entity(ies) named above and may contain information which is privileged a= nd/or confidential. If you are not the intended recipient, be aware that a= ny disclosure, copying, distribution, dissemination or use of the contents = of this message is prohibited. If you received this message in error, plea= se notify the sender immediately.

--0016e647622a0543b4046b7e4a24--