Repository navigation
pm.max_requests should be set #2142
Description
Activity
@theCalcaholic, if you think it makes sense, I can create a PR. Waiting for your confirmation though.
Thank you, yes, makes total sense. I'll happily merge a PR or can do it myself. Whatever you prefer :)
However, this would require not just a change to the template (etc/ncp-templates/php/pool.d.www.conf.sh) itself, but also a script for regenerating it on update (so inupdates/<version>.sh- compare1.58.0.sh).- Reacted by Tobias Knöppler
According to the official Nextcloud server tuning guide, PHP-FPM should be configured with
pm.max_requestsset, to prevent memory leaks.I am in a situation where workers consume increasing amounts of memory. I suspect this is to my configuration of the preview generation (enabled HEIC, PDF). I assume it is normal behavior, that workers do not actively free their allocated memory.
pm.max_requestssolves the problem by limiting worker lifespan.I suggest to make the value configurable with some reasonable default (e.g., 500).