Turning on Drupal performance caching (to see if overzelous regular caching will take a break)
So still trying to find out why the binary logs for our WSF2008 development site fill up the alloted disk space and shut down MySQL once every couple of days or, as yesterday, twice a day.
Searched for "drupal keeps refreshing cache" and found a wonderful pro-Drupal pitch with this reminder:
Drupal has a great cache feature that allows for very large and high traffic sites to cut down the number of database queries. On some sites it can become common to have up to 1,000 or so queries for each page view. This high number of queries can quickly start slowing a website to a crawl, especially a site with a substantial amount of traffic. With Drupal, there is a built in caching feature that will essentially store all the data from the "rendered" page into the database. This will change the number of queries from 1,000 to 1 which will improve performance considerably. You can then choose to refresh the cache data whenever you want to such as every 5 minutes, 20 minutes or every hour.
Turned Caching mode on, setting it to "Normal" and set Minimum cache lifetime to one hour.
Which is not what one normally does on a dev site. I don't think this is our issue, but maybe setting a cache lifetime can't hurt.