Java: JDBC Database connection pool

Question

HI: I have a multi thread Java database application, we have to create a customized database pooling. The reason is that some of our preparedstatement has to be cached in the co

Answer 1

Using synchronized will cost you about 1-2 microseconds. If this is critical to you, you shouldn't be using JDBC. IMHO. Just accessing a service over a TCP connection is likely to cost 100 micro-seconds and many JDBC databases have a latency of 1-10 milli-seconds.

I suspect that a few milliseconds per query/update is fine for you in which case using synchronization is unlikely to matter.

Depending on how many threads you have, you can have a thread local connection for each thread. This reduces the overhead as much as possible.

Answer 2

You have a multi-threaded application, but do many threads use the same database connection at the same time ? As the PreparedStatement cache will be done at the Connection level, if you connections are used by a single Thread at a time (which I think should be the case), you do not need synchronization.