In this case, it was me just using ps and top and seeing the php processes come and go rapidly.by jayj - Php-fpm Mailing List - English
I know there is an open bug about an alternative way to manage fpm processes, though I don't know the current state (except that it's open). However, I don't think the dynamic pool is bad, but it needs a few tweaks. First off, the standard apache 'min/max spare servers' concept only works for heavily loaded servers. I need a system to *slowly* ramp up and spin down php processes as load increasby jayj - Php-fpm Mailing List - English
philipp Wrote: > @jayi sour idea looks good but it won't be > possible to cache 404 pages based on the response > type... Cause all 404 pages will be text/html or > something like that independent of the "real" > response-type. Sure, I could add a separate 404 handler: location / { response-type =~ [ 'text/css', 'image/gif', 'image/jpeg', 'application/by jayj - How to...
Hi, I basically want to solve the same problem (static content generated with CGI variables) in a more generic case. Basically my idea was to somehow limit caching based on the Content-type of the proxied request rather than the location. It might look something like this: (I know this isn't valid) location / { response-type =~ [ 'text/css', 'image/gif', 'image/jpeg', 'appby jayj - How to...