I'm doing a project for a $CLIENT who has requested that I build out a small
web farm capable of serving 1M hits an hour average and peak traffic to
3M/hour. No problem there but when building the systems we got into a debate
about how he wants the OS built. Basically he said DO NOT build a swap
partition or swap file. I asked why and his response was "These are cookie
cutter web servers that do nothing other than serve apache requests. They
have nothing else on them so we'll run apache up to XXX for MaxClients and
MaxSpareServers (just shy of running the box out of memory) and leave it. "

He's the $CLIENT and I'l build it the way he requests but my questions
are...


   1. Would/Have you run a web server without swap? (they have 500Gb drives
   in them so there's room for a swap partition.)
   2. Any benefits or drawbacks to doing this?   (in context of a pure
   webserver that does nothing else but serve pages as part of the pool it is a
   member of.)


Happy Friday!


cheers,
-shane
--
_______________________________________________
Discuss mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to