Skip to content

Fix #1410 docs(rust-fil-proofs): note that locked memory as root could trigger OOM #1413

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

Merged
merged 1 commit into from
Feb 15, 2021
Merged

Fix #1410 docs(rust-fil-proofs): note that locked memory as root could trigger OOM #1413

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 README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -190,8 +190,8 @@ assemble each nodes parents and perform some prehashing. This setting is not ena
setting `FIL_PROOFS_USE_MULTICORE_SDR=1`.

Best performance will also be achieved when it is possible to lock pages which have been memory-mapped. This can be
accomplished either by running the process as root, or by increasing the system limit for max locked memory with `ulimit
-l`. Two sector size's worth of data (for current and previous layers) must be locked -- along with 56 *
accomplished by running the process as a non-root user, and increasing the system limit for max locked memory with `ulimit
-l`. Alternatively, the process can be run as root, if its total locked pages will fit inside physical memory. Otherwise, the OOM-killer may be invoked. Two sector size's worth of data (for current and previous layers) must be locked -- along with 56 *
`FIL_PROOFS_PARENT_CACHE_SIZE` bytes for the parent cache.

Default parameters have been tuned to provide good performance on the AMD Ryzen Threadripper 3970x. It may be useful to
Expand Down