Hawkin
/
arangodb
mirror of https://gitee.com/bigwinds/arangodb
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Doc - Recommend overcommit_memory 0 or 1 on Linux (planning#3151) (#7501)

This commit is contained in:
Simran 2018-11-28 07:45:35 -08:00 committed by sleto-it
parent 2d4b38600f
commit 3726fb55ad
1 changed files with 4 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
Documentation/Books/Manual/Installation/LinuxOSConfiguration.md
View File

@ -40,18 +40,13 @@ killing ArangoDB too eagerly on Linux.
### Over-Commit Memory
For the MMFiles storage engine, execute
The recommended kernel setting for `overcommit_memory` for both MMFiles and
RocksDB storage engine is 0 or 1. The kernel default is 0.
You can set it as follows before executing `arangod`:
sudo bash -c "echo 0 >/proc/sys/vm/overcommit_memory"
before executing `arangod`.
For the RocksDB storage engine, execute
sudo bash -c "echo 2 >/proc/sys/vm/overcommit_memory"
before starting.
From [www.kernel.org](https://www.kernel.org/doc/Documentation/sysctl/vm.txt):
- When this flag is 0, the kernel attempts to estimate the amount
@ -63,17 +58,6 @@ From [www.kernel.org](https://www.kernel.org/doc/Documentation/sysctl/vm.txt):
- When this flag is 2, the kernel uses a "never overcommit"
policy that attempts to prevent any overcommit of memory.
Note that then using an `overcommit_memory` setting of 2, this will by default allow
processes to use all swap space but only half of the available RAM. This can be changed
by adjusting the value of `overcommit_ratio` as well.
From [www.kernel.org](https://www.kernel.org/doc/Documentation/sysctl/vm.txt):
- When overcommit_memory is set to 2, the committed address
space is not permitted to exceed swap plus this percentage
of physical RAM.
### Zone Reclaim
Execute