I'm wondering if Turbine has a PreparedStatement caching mechanism along
with its db connection caching mechanism...
A co-worker of mine found a tuning document that said that reusing a
PreparedStatement is faster than using a regular Statement or even
creating a new PreparedStatement for each call. So he decided to run
a quick test.
Here are the average response times per JDBC call that he came up with:
A regular Statement: 246 ms (that's a quarter of a second)
A fresh PreparedStatement: 240 ms
A reused PreparedStatement: 4 ms (Wow!)
Has anyone else found similar results? If the performance improvement
is anywhere close to the same on other databases too (this test was done
with DB2), then I would bet that Torque has a PreparedStatement caching
mechanism along with its db connection caching mechanism. Is that true?
Or maybe it is impossible to reuse a PreparedStatement across
transaction boundaries, which would eliminate any hopes of caching them.
????
Any feedback on what others have found would be greatly appreciated.
Thanks!
Jonathan Carlson
[EMAIL PROTECTED]
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
