[DOCS-5108] Comment on: "manual/reference/transparent-huge-pages.txt" Created: 25/Mar/15 Updated: 11/Jan/17 Resolved: 07/Aug/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux mint debian edition Location: http://docs.mongodb.org/manual/reference/transparent-huge-pages/ |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 29 weeks ago | ||||||||
| Description |
|
Hi, As we can see here, there is now a double check on Transparent Huge Page: But When I use the 'In boot Time Configuration' suggestion, only transparent_hugepage/enable is set to never From Transparent Huge Page documentation : == Boot parameter == You can change the sysfs boot time defaults of Transparent Hugepage Because of that I still got a warning when running mongo on transparent_hugepage/defrag. Because of that, I think either the first solution is incomplete, or not adequate. Thank's for reading ! |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |
| Comment by Kay Kim (Inactive) [ 07/Aug/15 ] |
|
Duplicate of |
| Comment by Max Polk [ 05/May/15 ] |
|
Verified that the defrag is examined without regard to the enabled: $ cat /sys/kernel/mm/transparent_hugepage/enabled Therefore, the fix to this bug is to first look at transparent_hugepage/enabled, and if it is never, don't bother looking at the irrelevant transparent_hugepage/defrag setting. |