Re:Hire HN: Apache is crashing every hour. Seeking Drupal/Ng...
by kranner on Wednesday September 01, 2010 @07:29AM
(#1652438)
Instead of watching it in 'top', I recommend installing munin: http://munin-monitoring.org/
The blurb from that site:
Munin is a networked resource monitoring tool that can help analyze resource trends and "what just happened to kill our performance?" problems. It is designed to be very plug and play. A default installation provides a lot of graphs with almost no work.
Proof: You will have 0 memory free and start using swap when the restart happens - type 'top' and watch this go down.
Fix: Use less threads. The number of concurrent users you can support is the # of pages you can serve up per second in each thread times the number of threads your server can handle. So a huge improvement can be caching. Cache pages, blocks, hell maybe your whole site. The cache hits will serve 10-100 times more responses per second than generating your entire page.
I consulted on a project that was having horrible server performance on a huge server with relatively static data. The way they produced pages was really poor and took 3 or 4 seconds. There is no way you can serve up a large number of concurrent requests with the turnaround time over a second. I added caching as a quick fix and they ended up just being happy that 99.9% of their pages served up in 1/100th of a second.