On a openSUSE Tumbleweed 20210111 test system I evaluate Nextcloud 20. The problem is that even the test system with only one user and only very few files gets ressource problems. Directly after Nextcloud login (with pm.max_children=10) or some minutes later (with pm.max_children=50), PHP-FPM gets stuck. The Nextcloud browser window is open, but idle. I already found, that the number of active PHP-FPM processes is constantly growing. http://localhost/status currently shows 19 active processes: pool: www process manager: dynamic start time: 14/Jan/2021:23:59:47 +0100 start since: 36467 accepted conn: 714 listen queue: 0 max listen queue: 0 listen queue len: 0 idle processes: 1 active processes: 19 total processes: 20 max active processes: 28 max children reached: 0 slow requests: 0 If I close the Nextcloud browser windows, the PHP-FPM active process count is not growing anymore, but it does also not decrease. Nextcloud 18 was running fine on the same test system with identical PHP-FPM configuration. This is my PHP-FPM configuration /etc/php7/fpm/php-fpm.d/www.conf: [www] user = wwwrun group = www listen = localhost:9000 listen = /var/run/php-fpm-www.sock listen.owner = wwwrun listen.group = www listen.mode = 0660 pm = dynamic pm.max_children = 50 pm.start_servers = 2 pm.min_spare_servers = 1 pm.max_spare_servers = 3 pm.status_path = /status ping.path = /ping access.log = /var/log/$pool.access.log catch_workers_output = yes php_flag[display_errors] = on php_admin_value[error_log] = /var/log/fpm-php.www.log php_admin_flag[log_errors] = on php_value[max_execution_time] = 60 I did not found a matching bug report at Nextcloud. Any idea, how I can debug this problem? My main questions are: What are the active PHP-FPM processes doing? Why the active PHP-FPM processes do not get idle after they have done their work? Greetings, Björn