Hi Devs,
I have a question I couldn't find an answer for online or by investigating
the HSQLDB code myself.
Is there a reason currently in the implementation that the Stateless aspect
of a Prepared Statement when compiled isn't stored in a global
non-connection level cache ?
I have a use case where connections are created and destroyed regularly and
each connection calls 100+ prepared statement creation and executions
during its lifecycle, in a test case that encompasses many other factors I
increased performances by creating a naive low level cache of the compiled
statement to be used each time a new PreparedStatement with a matching sql
string was created.
This had a massive benefit to performance because the statements being
compiled are quite complex.
Is this a feature that hasn't been implemented on purpose ? Or just an open
gap ?
Thanks,
Daniel Walsh
Software Dev
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
hsqldb-developers mailing list
hsqldb-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
