You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
This is an umbrella tracking the items that support topology-aware scheduling.
Why is this needed?
Currently, Katalyst supports
numa-binding
andnuma-exclusive
enhancements for thededicated_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
fix(qrm): fix bugs failed to restore checkpoint enhanced-k8s#7fix(qrm): fix bug overwriting hint in qrm checkpoint to nil enhanced-k8s#8feat(qrm): add native qos class to resource request enhanced-k8s#9fix(qrm): only get requested topology aware resources enhanced-k8s#10QRM Plugin
Reporter
MetaServer and Lifecycle Controller
Scheduler
Charts
The text was updated successfully, but these errors were encountered: