[SERVER-6780] MongoDB Server Should Handle NUMA Memory Policy Intelligently Created: 16/Aug/12 Updated: 07/Aug/19 Resolved: 15/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Won't Fix | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Dev Tools 2019-05-20 | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
Back when we identified NUMA as a problem for mongod, we talked about possibly having the mongod intelligently manage NUMA policies itself. |