On Apr 5, 2011, at 7:54 AM, Pete French wrote: >> Having swap provides some cushion. Swap kind of smooths any bursts. (And it >> can >> also slow things down as a side effect) > > This is why I got rid of it - my application is a lot of CGI scripts. The > overload condition is that we run out of memory - and we run *way* out > of memory .... its never just a little overflow, it;s either handleable or > completely crushed. But swap makes that mre llikely to happen, because > as the processes are swapped out they run slower, take longer to > finish and thus use memory for longer. > > What I saw was that as soon as any web server would start tos wap it would > swftly fall down. Without swap they stay up, but reject requests. Its a better > failure mode...
You'll be better off providing swap space with every machine, and tuning Apache's MaxClients to a suitable value such that you don't swap excessively under load spikes. Without any swap, the system will be unable to page out unused portions of processes and will handle less load than it would with swap available. Regards, -- -Chuck _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
