I'm not very good at debugging database related problems but I agree with Geoff that this definitely sounds like a problem with CF waiting for database threads to timeout.
You didn't mention whether you have maintain connections across client requests enabled? Try disabling that and limiting connections to, say, 10 since you have max sim reqs set to 12. See what effect that has. As Geoff indicates, you'll probably have to experiment with the settings until you can get a little more information about where exactly the problem is occurring. One thing we ended up doing was adjusting the underlying JRun JDBC pool handling, making the skimmer run more often and a few other tweaks. I don't have the details to hand since I'm not part of the ops team that manage that aspect of our servers. On Thu, 16 Dec 2004 20:53:30 +1100, Ryan Sabir <[EMAIL PROTECTED]> wrote: > This is CFMX 6.1 with the latest updater (August 25) as well as hotfix > 53486 thrown in for good measure. I'm using the DB drivers that came > with CF. > > The DB settings are: > I'm not limiting connections, should I be? > Max Pooled Statements : 1000 > Timeout (min) 20: Interval (min) 7 > Login Timeout (sec) : 30 > > I also have Max Simultaneous requests set at 12, and timeout requests > after 15 seconds. > > The site is getting about 8 hits per second, most of them kicking off > a bunch of queries. It does about 5 G of traffic a day, most of that > is from a bunch of discussion forums. Its running on a single 3Ghz P4 > box with a GIG of RAM, the database is a shared one at the hosting > provider. > > The site is : http://www.essentialbaby.com.au/ if you want to > see it in action. Its one we inherited about a year ago in a really > bad state, and have been slowly rewriting it to make it more > efficient. --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
