Ed Park wrote:
> If your pages are not homogeneous in database
> usage (i.e., some pages are much heavier than others), then throttling by
> number of connections or throttling based on webserver load doesn't help
> that much. You need to throttle based on database server load. This requires
> some sort of mechanism whereby the webserver can sample the load on the
> database server and throttle accordingly. Currently, we just mount a common
> NFS fileserver, sample every minute, and restart the webserver if db load is
> too high, which works OK.
You could also just use an access handler that turns new requests away
with a simple "too busy" page when the database is hosed, rather than
actually restarting the server.
- Perrin
