[SERVER-25984] Don't issue numactl --interleave=all warning when bound to a single numa node Created: 06/Sep/16 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | neweng, platforms-re-triaged, save-for-celina | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Sprint: | Service Arch 2022-09-05 |
| Participants: |
| Description |
|
Currently we issue a warning when mongod is run on a numa-aware machine in any configuration other than --interleave=all. We should only do this when not bound to a single numa node since binding to a single node is generally even better than interleaving. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 21/Dec/21 ] |
|
We haven’t heard back from you in at least 1 year, so I'm going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. |