starlingx/docs
Code Issues Proposed changes
docs/doc/source/admintasks/isolating-cpu-cores-to-enhance-application-performance.rst
Juanita-Balaraj 0c4aa91ca4 Updated Patch Set 5 to include review comments 
Changed name of file to:
admin-application-commands-and-helm-overrides.rst

Updated Strings.txt

Updated formatting issues:
installing-and-running-cpu-manager-for-kubernetes.rst

Updated Patch Set 4 to include review comments

Admin Tasks Updated

Changed name of include file to:
isolating-cpu-cores-to-enhance-application-performance.rest

Change-Id: I0b354dda3c7f66da3a5d430839b5007a6a19cfad
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Signed-off-by: Stone <ronald.stone@windriver.com>
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
2021-01-11 23:40:36 -05:00

2.5 KiB
Raw Blame History

Isolate the CPU Cores to Enhance Application Performance

supports running the most critical low-latency applications on host CPUs which are completely isolated from the host process scheduler.

This allows you to customize Kubernetes CPU management when policy is set to static, or when using CMK with policy set to none so that high-performance, low-latency applications run with optimal efficiency.

The following restrictions apply when using application-isolated cores in the Horizon Web interface and sysinv:

  • There must be at least one platform and one application core on each host.

    Warning

    The presence of an application core on the node and nodes missing this configuration will fail.

For example:

~(keystone)admin)$ system host-lock worker-1
~(keystone)admin)$ system host-cpu-modify  -f platform -p0 1 worker-1
~(keystone)admin)$ system host-cpu-modify  -f application-isolated -p0 15 worker-1
~(keystone)admin)$ system host-cpu-modify  -f application-isolated -p1 15 worker-1
~(keystone)admin)$ system host-unlock worker-1

All SMT siblings on a core will have the same assigned function. On host boot, any CPUs designated as isolated will be specified as part of the isolcpu kernel boot argument, which will isolate them from the process scheduler.

The use of application-isolated cores is only applicable when using the static Kubernetes CPU Manager policy, or when using CMK. For more information, see Kubernetes CPU Manager Policies <kubernetes-cpu-manager-policies>, or Install and Run CPU Manager for Kubernetes <installing-and-running-cpu-manager-for-kubernetes>.

When using the static CPU manager policy before increasing the number of platform CPUs or changing isolated CPUs to application CPUs on a host, ensure that no pods on the host are making use of any isolated CPUs that will be affected. Otherwise, the pod(s) will transition to a Topology Affinity Error state. Although not strictly necessary, the simplest way to do this on systems other than AIO Simplex is to administratively lock the host, causing all the pods to be restarted on an alternate host, before changing CPU assigned functions. On AIO Simplex systems, you must explicitly delete the pods.

partner