I will look at writing up a patch for the single evictor thread. The other reply indicating that a team wrote an addon for marking connections dead indicates a need for a higher throughput mechanism for removing bad connections from the pool. Ideally since the DBCP library has a connection wrapper class, code could be added to all methods in the wrapper class to mark a connection as dead and not put it back into the pool.
-----Original Message----- From: Mark Thomas [mailto:[email protected]] Sent: Tuesday, February 24, 2009 1:43 AM To: Commons Users List Subject: Re: [DBCP] performance and scalability enhancements Todd Carmichael wrote: > Our site is using DBCP in several different applications. Our site has > high scalability requirements and some areas of DBCP and Pooling have > needed tuning in order to scale. I am soliciting feedback on these > changes. If the projects DBCP/POOL would/could make use of these > changes and to present a problem that we still having. > > 1) A single eviction thread for cleanup of stale connections. Our site > can have hundreds of database connection pools. An evictor thread per > connection pool puts a strain on the OS. > 2) testOnBorrow causes far too much overhead on our site and limits > performance. We have implemented a testOnBorrow after a X milliseconds. > Meaning, it will only test the connection if the connection has NOT been > tested for X milliseconds. Both enhancements sound useful. Can you create a Jira entry and attach a patch? Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
