Weblogic connection pools (JDBC)
- From: "Greg Norris" <spikey.mcmarbles@xxxxxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 14 Dec 2006 17:57:55 -0600
Is there any sort of baseline recommendation for the
StatementCacheSize setting when using Weblogic connection pooling?
I'm involved in some load testing of a 3rd-party application, and the
only significant issue we're seeing is a parse-to-execute ratio of
(essentially) 1:1. I've been told that we're using the default cache
size of 10 statements, which sounds woefully inadequate to me... I'm
tempted to ask for a substantial increase, such as to 50 or 100.
Unfortunately I'm not Weblogic-savvy, and so don't have any real
appreciation for the additional resources this would require on the
appserver. I realize this is rather vague, but would appreciate any
suggestions that I might use as a starting point.
For what it's worth, I do intend to ask our vendor contact if they
have any recommendations on this matter. It might take a few days to
get an answer, however, so I thought it would be worth checking into
here as well.
Thanx!
--
"I'm too sexy for my code." - Awk Sed Fred.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
