As an alternative, simply reboot the server whenever response time slows to an unacceptable level. Oh, say 30+ seconds for a response is my maximum lag threshold, although others might say 5 or 10 is really a maximum.
How often should we reboot the server?
Well, that depends on how long a reboot takes. If it takes 3 minutes to reboot, why not reboot once an hour? Or if it takes 10 minutes to reboot, why not reboot every 3 hours?
Come on, people, this is not rocket science!! At least reboot once a day.
-- An increasing frustrated and impatient "Uncle Ed" Poor
On Thu, 6 Feb 2003, Poor, Edmund W wrote:
As an alternative, simply reboot the server whenever response time slows to an unacceptable level. Oh, say 30+ seconds for a response is my maximum lag threshold, although others might say 5 or 10 is really a maximum.
That would be rather silly. Perhaps taking the db down for a few moments would keep people away and thus reduce traffic, but a reboot isn't necessary for that.
As it is, we restart Apache every half hour -- in a "graceful" restart mode that doesn't interrupt downloads.
How often should we reboot the server?
At most a couple times per year, for kernel upgrades or physical relocation of the server.
If the server crashes completely (as it's done a couple times in the past several months), then it also needs to be rebooted, but this is a very rare occurance.
Well, that depends on how long a reboot takes. If it takes 3 minutes to reboot, why not reboot once an hour? Or if it takes 10 minutes to reboot, why not reboot every 3 hours?
Come on, people, this is not rocket science!! At least reboot once a day.
I take it you've been doing a lot of work with Microsoft products? :)
-- brion vibber (brion @ pobox.com)