From 133443bd144de6bec11894099871fa8ec64112c7 Mon Sep 17 00:00:00 2001 From: alexey-milovidov Date: Wed, 23 Jun 2021 00:09:10 +0300 Subject: [PATCH] Update tips.md --- docs/en/operations/tips.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/docs/en/operations/tips.md b/docs/en/operations/tips.md index 0b74ae95b06..4291b91b41d 100644 --- a/docs/en/operations/tips.md +++ b/docs/en/operations/tips.md @@ -30,14 +30,6 @@ Do not disable overcommit. The value `cat /proc/sys/vm/overcommit_memory` should $ echo 0 | sudo tee /proc/sys/vm/overcommit_memory ``` -## Huge Pages {#huge-pages} - -Always disable transparent huge pages. It interferes with memory allocators, which leads to significant performance degradation. - -``` bash -$ echo 'madvise' | sudo tee /sys/kernel/mm/transparent_hugepage/enabled -``` - Use `perf top` to watch the time spent in the kernel for memory management. Permanent huge pages also do not need to be allocated. @@ -91,6 +83,15 @@ The Linux kernel prior to 3.2 had a multitude of problems with IPv6 implementati Use at least a 10 GB network, if possible. 1 Gb will also work, but it will be much worse for patching replicas with tens of terabytes of data, or for processing distributed queries with a large amount of intermediate data. +## Huge Pages {#huge-pages} + +If you are using old Linux kernel, disable transparent huge pages. It interferes with memory allocators, which leads to significant performance degradation. +On newer Linux kernels transparent huge pages are alright. + +``` bash +$ echo 'madvise' | sudo tee /sys/kernel/mm/transparent_hugepage/enabled +``` + ## Hypervisor configuration If you are using OpenStack, set