-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bill,

On 10/16/2009 5:36 PM, Bill Davidson wrote:
> Bill Davidson wrote:
>>Could maxOpenPreparedStatements possibly fix this?
> 
> Apparently it does.

Glad to get the bottom of this problem, though I'm not entirely sure
where it leaves you.

> The DBCP config docs need a better warning on poolPreparedStatements:
> 
> "*NOTE* - Make sure your connection has some resources left for the
> other statements."
> 
> just doesn't quite cut it.

I see you've cross-posted to commons-user. That's good, but you probably
want to file an actually bug report / enhancement request for the
documentation.

As for your performance issues, I'm not sure what to tell you. There are
probably opportunities for you to optimize certain queries, but if
changing the caching of prepared statements is changing your performance
significantly, then I wouldn't be surprised if you are simply running
into performance problems with Oracle's query parser. Again, talking to
a DBA would be very beneficial.

I'm curious about the usefulness of caching prepared statements in
general, though. What is the default maxOpenPreparedStatements setting
and what did you set it to in order to get it to work out well for you?
If you have 100 different prepared statements in your code and you are
only allowing a connection to cache, say, 5 of them, then I have to
expect that you'll be constantly thrashing your cache as new statements
are prepared and executed. Do you see a performance gain between
disabling statement caching and enabling it, but setting the cache size
relatively low?

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrcewcACgkQ9CaO5/Lv0PDfhgCff1Q4gyvajWR/oYyZSiRJhX+I
RQkAoImJjWXr5dYOK37kxDttddhEBU4X
=b9v7
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to