Paulo Gaspar wrote:
>When I considered that [pooling prepared statements]
>it was more pain than gain.
>
>Lots of possible side effecets to consider and not a great
>performance gain in general.
I disagree. When we implemented PreparedStatement pooling in a system that
was already using Connection pooling, we saw a dramatic increase in
performance and a dramatic decrease in the load on the database--largely due
to the parse rate dropping.
(This was on an Oracle (8.1.5/8.1.6) database. Your mileage may vary. I
might be able to pull up the numbers if you're interested.)
If you'd like to give it a try, I submitted a connection/prepared statement
pooling mechanism that is largely compatible with the existing
GenericDataSource a couple of weeks ago. It also supports a pseudo-Driver,
so you can add pooling to a code-base that thinks it's using straight-JDBC.
See http://marc.theaimsgroup.com/?l=struts-dev&m=97967619230491 and
http://www.mail-archive.com/struts-dev@jakarta.apache.org/msg00035.html.
- Rod Waldhoff <[EMAIL PROTECTED]>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
