Comments on: Connection Pool Showdown http://javatech.org/2008/02/connection-pool-showdown/ The Bleeding Edge of Java Technology Wed, 03 Sep 2008 17:21:16 -0400 http://wordpress.org/?v=2.8 hourly 1 By: Anonymous http://javatech.org/2008/02/connection-pool-showdown/comment-page-1/#comment-272 Anonymous Wed, 20 Aug 2008 14:58:09 +0000 http://javatech.org/?p=29#comment-272 Nice work. A couple of questions. I'm confused by "...and confirmed that DBCP is the fastest pool in the West, so long as there isn’t any complicated synchronization being done by the code using DBCP!" You mean that DBCP is fastest if the code calling DBCP doesn't use complicated synchronisation? If the code calling DBCP has performance problems, then of course DBCP can't help. Wouldn't the same be true for c3p0 and Proxool? Will you publish your test case for review? What version of each package did you use? thanks, matt Nice work. A couple of questions.

I’m confused by “…and confirmed that DBCP is the fastest pool in the West, so long as there isn’t any complicated synchronization being done by the code using DBCP!” You mean that DBCP is fastest if the code calling DBCP doesn’t use complicated synchronisation? If the code calling DBCP has performance problems, then of course DBCP can’t help. Wouldn’t the same be true for c3p0 and Proxool?

Will you publish your test case for review?

What version of each package did you use?

thanks,
matt

]]> By: Darren Hicks http://javatech.org/2008/02/connection-pool-showdown/comment-page-1/#comment-271 Darren Hicks Sat, 21 Jun 2008 04:34:45 +0000 http://javatech.org/?p=29#comment-271 Well, I guess it doesn't really have to be all that complicated to create an issue with DBCP. The thing is that DBCP's methods for acquiring and returning connections to the pool are synchronized which make it possible for deadlocks to occur amongst client threads. With C3P0, this synchronization isn't present ( on the returns, at least ) and therefore the deadlocks don't happen. C3P0 has a separate pool of helper threads which are responsible for getting the threads back into the pool without synchronization. Well, I guess it doesn’t really have to be all that complicated to create an issue with DBCP. The thing is that DBCP’s methods for acquiring and returning connections to the pool are synchronized which make it possible for deadlocks to occur amongst client threads. With C3P0, this synchronization isn’t present ( on the returns, at least ) and therefore the deadlocks don’t happen. C3P0 has a separate pool of helper threads which are responsible for getting the threads back into the pool without synchronization.

]]> By: jer http://javatech.org/2008/02/connection-pool-showdown/comment-page-1/#comment-270 jer Wed, 18 Jun 2008 23:22:55 +0000 http://javatech.org/?p=29#comment-270 Can you explain what you mean by "complicated synchronization?" What in particular is it I need to watch out for and why? Can you explain what you mean by “complicated synchronization?” What in particular is it I need to watch out for and why?

]]>