Skip to content

correct unit in server memory recommendations #15698

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MrRinkana wants to merge 1 commit into
base: master
Choose a base branch
from
Open

correct unit in server memory recommendations #15698

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions admin_manual/installation/server_tuning.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -180,9 +180,9 @@ Key parameters

Measure the average RSS of a running pool::

ps --no-headers -o rss -C php-fpm | awk '{sum+=$1; count++} END {if (count>0) print sum/count/1024 " MB"; else print "No php-fpm processes found"}'
ps --no-headers -o rss -C php-fpm | awk '{sum+=$1; count++} END {if (count>0) print sum/count/1024 " MiB"; else print "No php-fpm processes found"}'

A typical Nextcloud worker uses **50–100 MB** (more if Imagick or LDAP is loaded).
A typical Nextcloud worker uses **50–100 MiB** (more if Imagick or LDAP is loaded).
Leave headroom for the OS, web server, database, and cache. Setting ``pm.max_children``
too high causes swapping, which is worse than queuing.

Expand Down