Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8874

Ensure balance allocation of pods across NUMA Nodes - balance-numa-node

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Node
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Ensure that multiple instances of partner application (represented by Pods) are placed equally across compute die's on the same processor (See diagram below) so that one compute die doesn't get overloaded while others run idle.

      The INTEL CPU at hands is called Clearwater Forest, single socket, in SNC-3 mode (Sub-NUMA Clustering 3). 

       

      Example:

      A pod, pod#1, is scheduled to run.

      The NUMA-aware scheduler select the appropriate worker node: Worker node 0 is selected.

      Then the Kubernetes Topology Manager select the appropriate NUMA Zone so that all the required CPU comes from the same NUMA Zone: NUMA Zone 0 is selected.

      A subsequent pod, pod#2 is scheduled.

      The NUMA-aware scheduler select the appropriate worker node: Worker node 0 is selected.

      Then the Kubernetes Topology Manager select the appropriate NUMA Zone so that all the required CPU comes from the same NUMA Zone: NUMA Zone 1 or Zone 2 should be selected ensuring  resources are properly utilized  when multiple pods are deployed on the same worker node. NUMA Zone 1 is selected.

       

      Possible reference:

              gausingh@redhat.com Gaurav Singh
              brault@redhat.com Bertrand Rault
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                None
                None