Skip to content

correct unit in server memory recommendations - #15698

Open
MrRinkana wants to merge 2 commits into
nextcloud:masterfrom
MrRinkana:patch-1
Open

MrRinkana wants to merge 2 commits into
nextcloud:masterfrom
MrRinkana:patch-1

Conversation

@MrRinkana

Copy link
Copy Markdown

ps -o rss reports values in kikibytes, not kilobytes: https://man7.org/linux/man-pages/man1/ps.1.html

The command iself then uses 1024 to convert to MiB

As the section is about memory estimations, accuracy is important

Changes MB to MiB in two locations: the command output and text showing common nextcould fpm memory use

ps -o rss reports values in kikibytes, not kilobytes: https://man7.org/linux/man-pages/man1/ps.1.html

The command iself then uses 1024 to convert to MiB

As the section is about memory estimations, accuracy is important

Signed-off-by: Rinkana <39345772+MrRinkana@users.noreply.github.com>
@tflidd

tflidd commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

on debian trixie they say that they use kilobytes....

       rss         RSS       resident set size, the non-swapped physical memory
                             that  a  task  has  used  (in  kilobytes).  (alias
                             rssize, rsz).

@MrRinkana

Copy link
Copy Markdown
Author

@tflidd
That is an documentation issue in procps which was fixed in more recent versions; it has always actually been kikibytes.

https://gitlab.com/procps-ng/procps/-/merge_requests/211

Also the division done in the command here is by 1024 which means it cannot be MB (and if PS had been returning KB the resulting value was nonsensical: neither MB or MiB)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants