mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
48 lines
1.5 KiB
Plaintext
48 lines
1.5 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * scalability_and_performance/low_latency_tuning/cnf-tuning-low-latency-nodes-with-perf-profile.adoc
|
|
|
|
[id="how-to-run-podman-to-create-a-profile_{context}"]
|
|
= How to run podman to create a performance profile
|
|
// Is this example required for a specific reason?
|
|
The following example illustrates how to run `podman` to create a performance profile with 20 reserved CPUs that are to be split across the NUMA nodes.
|
|
|
|
Node hardware configuration:
|
|
|
|
* 80 CPUs
|
|
* Hyperthreading enabled
|
|
* Two NUMA nodes
|
|
* Even numbered CPUs run on NUMA node 0 and odd numbered CPUs run on NUMA node 1
|
|
|
|
Run `podman` to create the performance profile:
|
|
|
|
[source,terminal,subs="attributes+"]
|
|
----
|
|
$ podman run --entrypoint performance-profile-creator -v /must-gather:/must-gather:z registry.redhat.io/openshift4/ose-cluster-node-tuning-operator:latest --mcp-name=worker-cnf --reserved-cpu-count=20 --rt-kernel=true --split-reserved-cpus-across-numa=true --must-gather-dir-path /must-gather > my-performance-profile.yaml
|
|
----
|
|
|
|
The created profile is described in the following YAML:
|
|
|
|
[source,yaml]
|
|
----
|
|
apiVersion: performance.openshift.io/v2
|
|
kind: PerformanceProfile
|
|
metadata:
|
|
name: performance
|
|
spec:
|
|
cpu:
|
|
isolated: 10-39,50-79
|
|
reserved: 0-9,40-49
|
|
nodeSelector:
|
|
node-role.kubernetes.io/worker-cnf: ""
|
|
numa:
|
|
topologyPolicy: restricted
|
|
realTimeKernel:
|
|
enabled: true
|
|
----
|
|
|
|
[NOTE]
|
|
====
|
|
In this case, 10 CPUs are reserved on NUMA node 0 and 10 are reserved on NUMA node 1.
|
|
====
|