[SERVER-12033] Windows is not detecting NUMA settings Created: 10/Dec/13 Updated: 11/Jul/16 Resolved: 17/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | 2.5.4 |
| Fix Version/s: | 2.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alvin Richards (Inactive) | Assignee: | Mark Benvenuto |
| Resolution: | Done | Votes: | 1 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | Windows | ||||||||
| Participants: | |||||||||
| Description |
|
Problem: See
Appears that this check assumes that there is no NUMA impact for Windows. Solution: http://msdn.microsoft.com/en-us/library/windows/desktop/aa363804(v=vs.85).aspx Next Step: |
| Comments |
| Comment by Githook User [ 17/Dec/13 ] | |||||||||||||||||||||
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: | |||||||||||||||||||||
| Comment by Mark Benvenuto [ 13/Dec/13 ] | |||||||||||||||||||||
|
One option is to ask the user to disable it in the bios. I added this warning message. If you would like I can use Get/SetProcessAffinityMask to pin mongodb to one NUMA node, but there is no guarantee that Windows will not spill memory allocations over to other nodes once the current node runs low on memory. This may be more confusing to the user.
| |||||||||||||||||||||
| Comment by Asya Kamsky [ 13/Dec/13 ] | |||||||||||||||||||||
|
It's not clear there is an analogous "utility/command" - disabling NUMA in BIOS is one option though in some scenarios on some variants of OS/machines it's not even possible there. There are ways to start processes to bind to one NUMA node. Windows API has SetThreadAffinityMask - but all the threads that might be working on shared memory must run on the same core... | |||||||||||||||||||||
| Comment by Matt Kangas [ 13/Dec/13 ] | |||||||||||||||||||||
|
Note that on Linux, when you launch on a NUMA machine you will see:
Then, relaunching with the recommended command, the warning goes away.
Let's make sure Windows works similarly. |