Enable defer+madvise defragmention for THP by default #31
Conversation
|
I guess the settings could be a little more customized w- /sys/kernel/mm/transparent_hugepage/enabled - - - - - madvise |
the difference is that: w! overwrites existing data in the file. w- writes data only if the file is empty or unset.
|
@ventureoo |
Should fix it |
|
Kernel docs imply that setting defrag to 'madvise' would perform the stalling behavior seen in 'always', wouldn't 'defer' be more advantageous than 'defer+madvise' for interactivity? Update: Team Fortress 2 does not seem to allocate any hugepages at all if /transparent_hugepage/enabled is set to 'madvise' instead of 'always', this appears to be a global issue with TCMalloc: google/tcmalloc#85 |
Thanks for notice. I'll remove madvise for |
Due to possible regressions
ventureoo
force-pushed
the
thp-madvise
branch
from
71d8a92
to
f4bc377
Compare
|
@ptr1337 I've signed the last commit. Are there any objections to this PR? |
This should improve the performance of applications that use the tcmalloc memory allocator, which is used by Chromium/Electron and Valve's native games, among others.
Ref: https://github.com/google/tcmalloc/blob/master/docs/tuning.md#system-level-optimizations