2018-02-04 2:27 GMT+01:00 Yann Ylavic <ylavic....@gmail.com>:
> I'm not sure playing with 'max' is the the right thing to do in this
> case, it makes few sense to configure max_children on fpm lower than
> httpd's MaxRequestWorkers, they probably should be the same in the
> first place.
> Limits should indeed be imposed by the proxy (according to upstream
> capacity), but 'max' is kind of waste of resources here on the proxy
> side, the right/same MaxRequestWorkers on httpd should be enough (with
> possibly reasonable/agressive MaxSpareThreads/Servers) provided it
> does not exceed fpm's max_children.
Definitely, I agree. What I meant to say with the 'max' comment was that it
is a quick way to workaround the stall :)
Going to update users@ and the docs!