jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Schumacher <felix.schumac...@internetallee.de>
Subject Re: JDBC PreparedStatement Cache
Date Tue, 06 Sep 2016 18:33:44 GMT
Am 06.09.2016 um 20:22 schrieb Philippe Mouawad:
> Hi Felix,
> My answer below.
> Regards
>
> On Tuesday, September 6, 2016, Felix Schumacher <
> felix.schumacher@internetallee.de> wrote:
>
>> Hi all,
>>
>> we have a pool for PreparedStatements in AbstractJDBCTestElement, which
>> has a problem with the wrapped Connections, that are returned by our jdbc
>> pool. We could fix it, by unwrapping the pool-connection and using that as
>> key for the cache-map "perConnCache". But this unwrapping would be special
>> to the used pool implementation and we wanted to be independent :(
>>
>> Another thing is, that since jdbc 3.0 there seems to be support for
>> pooling/cacheing of PreparedStatements in the jdbc driver itself. It seems,
>> that most major vendors have implemented that cache (see
>> https://github.com/brettwooldridge/HikariCP/issues/488).
>>
>> Given these two bits of information I would opt to remove the perConnCache
>> in order to solve bug 60085.
>>
>> What do you think?
> +1 for me.
> Do you know if sqlserver has now a prepared statement pool in it driver ?
Looking at 
https://social.msdn.microsoft.com/Forums/en-US/3922b86a-867f-4c48-84d7-611258a3d3be/jdbc-driver-support-statement-caching?forum=sqldataaccess

it doesn't need to support it, since the server will support it out of 
the box.

Felix
>
>> Felix
>>
>>


Mime
View raw message