[DOCS-12903] Requirement for disabling THP in both init.d and tuned needs clarification Created: 21/Jul/19  Updated: 30/Oct/23  Resolved: 15/Nov/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Minor - P4
Reporter: Eric Sommer Assignee: Andrew Feierabend (Inactive)
Resolution: Fixed Votes: 1
Labels: THP
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-12902 Separately disabling THP defrag is no... Closed
Participants:
Days since reply: 4 years, 29 weeks, 3 days ago
Epic Link: DOCSP-1769

 Description   

Description

https://docs.mongodb.com/manual/tutorial/transparent-huge-pages/#init-script

IMPORTANT

If you are using tuned or ktune (for example, if you are running Red Hat or CentOS 6+), you must additionally configure them so that THP is not re-enabled. See Using tuned and ktune.

This is not 100% accurate. Disabling THP in tuned/ktune is sufficient. The motivation for disabling in both places (inti.d and tuned/ktune) is because conflicting settings can overwrite one another. But if THP is disabled in tuned, as long as it is not explicitly enabled in init.d, disabling in init.d is not technically necessary for THP to be disabled.

If the documentation is going to recommend both steps, it might be worth clarifying that the reason is to prevent a conflict. Otherwise, a reader might question why both steps are necessary.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)


Generated at Thu Feb 08 08:06:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.