Apache eats memory processes with long poll requests. The technology is long poll, as in this video: http://www.screenr.com/SNH

Due to the time checking cycle, when the page is repeatedly updated, the Apache processes are spawning and memory is clogged, since the maxClients on the Apache cost 256, then the Apache, crossing the border, hangs. Only restarting helps. The apache is worth the itk module. Php is connected as an Apache module.

  • one
    . long po l l - etki
  • If you are given an exhaustive answer, mark it as correct (a daw opposite the selected answer). - Nicolas Chabanovsky ♦

1 answer 1

Use Nginx as a proxy and better yet put php-fpm instead of apache for it. Otherwise, maxClients should be set very, very large, which in the end will still lead to the fall of Apache under load.

Nginx works well with slow clients and does an excellent job with loads. In conjunction with the Apache, he will unload it. And in conjunction with php-fpm you generally forget about a headache;)

UPD

Better yet, go to Web Sockets . The speed of work will increase, and the load will fall.