FTDC should accurately reflect whether multi-socket CPU's are pinned

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: 6.0.24
    • Component/s: None
    • None
    • Networking & Observability
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, there is confusion about when FTDC is returning CPU counts from clusters that may have pinned sockets on multi-socket machines.

      We derive the following from FTDC on MongoDB 6.0.24:

      numCores:48 
      numPhysicalCores:48 
      numCpuSockets:2 
      numaEnabled:false

       and lscpu will see:

      CPU(s): 96

      Can we add some indication of cpu pinning to hostInfo? Alternatively, is this already resolved by changes like numCoresAvailableToProcess in SERVER-83666?

        1. screenshot-1.png
          750 kB
          Chris Kelly

              Assignee:
              Unassigned
              Reporter:
              Chris Kelly
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: