commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: Commons Pool/DBCP minIdle Implementation
Date Fri, 15 Aug 2003 13:47:25 GMT

Howdy,
One way to do it would be to post an enhacenment request and bugzilla
and attach your patch (with any relevant files, e.g. unit tests) to the
bugzilla item.  Committers review this list periodically, and certainly
before every release.

Yoav Shapira
Millennium ChemInformatics


>-----Original Message-----
>From: Richard Wareing [mailto:wareing@rewc.com]
>Sent: Friday, August 15, 2003 9:45 AM
>To: commons-dev@jakarta.apache.org
>Subject: Commons Pool/DBCP minIdle Implementation
>
>Hello everyone,
>
>For a project I'm working on we needed the capability to have the
number
>of idle objects in the pool (database connections via DBCP in this
case)
>to stay at some minimum level for performance reasons.
>
>The main performance benefit I saw for this was X number of connections
>always being available in the event the pools connections became stale
>for some reason (e.g. database went down and came back up some time
>later).  For high latency database connections (>250ms) this equates to
>a substantial savings in query time as well as adds to the QOS (rather
>than having the first person in after the pool being cleaned out
trigger
>a new connection).
>
>Anyhow, I implemented the feature in commons-pool as well as
>commons-dbcp and I was wondering if you might consider it for
>integration into the main trees?  If so how does one go about
>contributing this to the project?  The changes were relatively trivial
>and IMHO :) really improve the performance and resilience of the
>package.
>
>Richard Wareing
>Software Engineer
>Reimer Technology Group
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org




This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.


Mime
View raw message