News for hackers. Stuff that matters.
Re:Surviving a traffic surge: Three techniques to scale your... by hybrid11 on Tuesday March 29, 2011 @02:56PM (#2383889)
what would you recommend instead?
Re:Surviving a traffic surge: Three techniques to scale your... by ceejayoz on Tuesday March 29, 2011 @03:08PM (#2383935)
Apache's memory usage should not exceed the available RAM on the machine. If you do that, it starts having to use swap, which drastically slows things down - if you're already getting lots of hits, it'll start a death spiral.

Apache's memory usage varies based on what modules are enabled and the code they're serving and a number of other factors.

The rule of thumb is to take the average free RAM when Apache isn't running, divide it by the average RAM usage of a single Apache process on your system, and set MaxClients to a couple under that value.

For example, on a 512MB Linode box, if you've got 450MB free when Apache isn't running, and Apache takes up 12MB per process, you'd allow about 35 at the most.

Re:Surviving a traffic surge: Three techniques to scale your... by hybrid11 on Tuesday March 29, 2011 @08:54PM (#2385278)
Makes sense, thanks for clarifying!
Re:Surviving a traffic surge: Three techniques to scale your... by powertower on Tuesday March 29, 2011 @03:57PM (#2384137)
Here is a good one: http://www.devside.net/articles/apache-performance-tuning

Was written a few years back for a Linode 128MB.