According to the official Nextcloud server tuning guide, PHP-FPM should be configured with pm.max_requests set, 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_requests solves the problem by limiting worker lifespan.
I suggest to make the value configurable with some reasonable default (e.g., 500).
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).