[DOCS-4577] Filesystem elevator recommendations Created: 23/Dec/14 Updated: 08/May/23 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Luke Prochazka | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 7 years, 29 weeks ago | ||||||||||||
| Description |
|
The current recommendation is the use the noop elevator policy, as per this DOC http://www.mongodb.org/about/ssd/#os-scheduler However, this is only a benefit in niche use cases, such as multiple mongod VM instances cohabiting the same virtual host with similar workloads connected to the same shared storage. I recommend the advice be changed to use the default cfq elevator policy instead. |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed by Emily Hall for Housekeeping on 7/27/16. Thank you! |