[Umbrella] Support topology-aware scheduling
caohe opened this issue · comments
This is an umbrella tracking the items that support topology-aware scheduling.
Why is this needed?
Currently, Katalyst supports numa-binding
and numa-exclusive
enhancements for the dedicated_cores
QoS class in the colocation scenario.
In situations outside of colocation, it is also necessary to be aware of the NUMA and device topology when scheduling and allocating resources, so as to improve the performance of containers. Furthermore, in this particular scenario, Katalyst's resource allocation strategy needs to be compatible with Kubernetes' native allocation strategy.
What would you like to be added?
-
APIs
-
QRM framework
-
QRM Plugin
-
Reporter
-
MetaServer and Lifecycle Controller
-
Scheduler
-
Charts