António P. P. Almeida
António P. P. Almeida
OOM killer is a kernel process that recovers memory that is thought to be the result of a runout process. Check this: http://lwn.net/Articles/317814/ This could be a php-fpm config issue...
You might want to look [here](http://groups.drupal.org/node/229898). This is probably due to the high number of cached connections for the FCGI upstream keepalive. Lower the value to 1 and see how...
I think that there's something in your site that triggers that. Have you checked the logs (php-fpm logs I mean)?
I can't help you there. What I can help you is to get Nginx working as a LB/reverse proxy replacing Varnish, with advantages IMHO. Unless you use very abstruse stuff...
Ok. Post your VCL file somewhere, so that I can suggest a reverse proxy config for Nginx.
I'm a hardly a Varnish connaisseur. But most of this stuff is already done by the Nginx config (80% out of the box): 1. No compression of images. 2. HEAD...
No, you don't need to. It's quite optimized in terms of IO. If you want it you can put it on a `tmpfs` partition.
BTW, are you receptive to testing the two setups and benchmark each approach?
Ok. This evening (I'm on CET ) I'll create a branch `varnish-cracker` and push the first attempt at getting it right.
Ok the first commit is in. I have to test it. Usually I set up different upstreams for videos, css/js, images, etc. This is a simplification. It's the load balancer...