Skip to content

Commit

Permalink
docs(rust-fil-proofs): note that locked memory as root could trigger …
Browse files Browse the repository at this point in the history
…OOM (#1413)
  • Loading branch information
neondragon committed Feb 15, 2021
1 parent 35ca38a commit 9b3bab2
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
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

0 comments on commit 9b3bab2

Please sign in to comment.