Cache of prepared statements in #319 uses per-connection cache, so in case of connection pool lots of queries are repeated in memory.
We can use "per-URL" kind of cache to share query texts and avoid parsing on connection renewals.
Current evaluation:
+ shared cache of parsed queries would reduce memory footprint of a connection pool
- additional cross-thread synchronization on con.prepareStatement might reduce throughput
- more complicated implementation might reduce performance and/or complicate support
Cache of prepared statements in #319 uses per-connection cache, so in case of connection pool lots of queries are repeated in memory.
We can use "per-URL" kind of cache to share query texts and avoid parsing on connection renewals.
Current evaluation:
+shared cache of parsed queries would reduce memory footprint of a connection pool-additional cross-thread synchronization oncon.prepareStatementmight reduce throughput-more complicated implementation might reduce performance and/or complicate support