mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
117 lines
5.3 KiB
Plaintext
117 lines
5.3 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
[id="cnf-tuning-low-latency-nodes-with-perf-profile"]
|
|
= Tuning nodes for low latency with the performance profile
|
|
include::_attributes/common-attributes.adoc[]
|
|
:context: cnf-low-latency-perf-profile
|
|
|
|
toc::[]
|
|
|
|
Tune nodes for low latency by using the cluster performance profile.
|
|
You can restrict CPUs for infra and application containers, configure huge pages, Hyper-Threading, and configure CPU partitions for latency-sensitive processes.
|
|
|
|
[id="cnf-create-performance-profiles"]
|
|
== Creating a performance profile
|
|
|
|
You can create a cluster performance profile by using the Performance Profile Creator (PPC) tool. The PPC is a function of the Node Tuning Operator.
|
|
|
|
The PPC combines information about your cluster with user-supplied configurations to generate a performance profile that is appropriate to your hardware, topology and use-case.
|
|
|
|
[NOTE]
|
|
====
|
|
Performance profiles are applicable only to bare-metal environments where the cluster has direct access to the underlying hardware resources. You can configure performances profiles for both {sno} and multi-node clusters.
|
|
====
|
|
|
|
The following is a high-level workflow for creating and applying a performance profile in your cluster:
|
|
|
|
* Create a machine config pool (MCP) for nodes that you want to target with performance configurations. In {sno} clusters, you must use the `master` MCP because there is only one node in the cluster.
|
|
|
|
* Gather information about your cluster using the `must-gather` command.
|
|
|
|
* Use the PPC tool to create a performance profile by using either of the following methods:
|
|
|
|
** Run the PPC tool by using Podman.
|
|
|
|
** Run the PPC tool by using a wrapper script.
|
|
|
|
* Configure the performance profile for your use case and apply the performance profile to your cluster.
|
|
|
|
include::modules/cnf-about-the-profile-creator-tool.adoc[leveloffset=+2]
|
|
|
|
include::modules/cnf-creating-mcp-for-ppc.adoc[leveloffset=+2]
|
|
|
|
include::modules/cnf-gathering-data-about-cluster-using-must-gather.adoc[leveloffset=+2]
|
|
|
|
[role="_additional-resources"]
|
|
.Additional resources
|
|
|
|
* xref:../support/gathering-cluster-data.adoc#nodes-nodes-managing[Gathering data about your cluster]
|
|
|
|
// * xref:../hosted_control_planes/hcp-troubleshooting.adoc#hcp-must-gather-cli[Gathering data for a hosted cluster by using the CLI]
|
|
|
|
include::modules/cnf-running-the-performance-creator-profile.adoc[leveloffset=+2]
|
|
|
|
include::modules/cnf-running-the-performance-creator-profile-offline.adoc[leveloffset=+2]
|
|
|
|
include::modules/cnf-performance-profile-creator-arguments.adoc[leveloffset=+2]
|
|
|
|
[id="cnf-create-performance-profiles-reference"]
|
|
=== Reference performance profiles
|
|
|
|
Use the following reference performance profiles as the basis to develop your own custom profiles.
|
|
|
|
include::modules/installation-openstack-ovs-dpdk-performance-profile.adoc[leveloffset=+3]
|
|
|
|
include::modules/cnf-telco-ran-reference-design-performance-profile-template.adoc[leveloffset=+3]
|
|
|
|
include::modules/cnf-telco-core-reference-design-performance-profile-template.adoc[leveloffset=+3]
|
|
|
|
include::modules/cnf-use-device-interrupt-processing-for-isolated-cpus.adoc[leveloffset=+1]
|
|
|
|
include::modules/cnf-configuring-workload-hints.adoc[leveloffset=+1]
|
|
|
|
include::modules/cnf-configuring-power-saving-for-nodes.adoc[leveloffset=+1]
|
|
|
|
[role="_additional-resources"]
|
|
.Additional resources
|
|
|
|
* xref:../scalability_and_performance/cnf-tuning-low-latency-nodes-with-perf-profile.adoc#cnf-about-the-profile-creator-tool_cnf-low-latency-perf-profile[About the Performance Profile Creator]
|
|
|
|
* xref:../scalability_and_performance/cnf-provisioning-low-latency-workloads.adoc#cnf-configuring-high-priority-workload-pods_cnf-provisioning-low-latency[Disabling power saving mode for high priority pods]
|
|
|
|
* xref:../scalability_and_performance/cnf-tuning-low-latency-nodes-with-perf-profile.adoc#managing-device-interrupt-processing-for-guaranteed-pod-isolated-cpus_cnf-low-latency-perf-profile[Managing device interrupt processing for guaranteed pod isolated CPUs]
|
|
|
|
include::modules/cnf-cpu-infra-container.adoc[leveloffset=+1]
|
|
|
|
include::modules/cnf-configuring-hyperthreading-for-a-cluster.adoc[leveloffset=+1]
|
|
|
|
include::modules/cnf-managing-device-interrupt-processing-for-guaranteed-pod-isolated-cpus.adoc[leveloffset=+1]
|
|
|
|
include::modules/cnf-about-irq-affinity-setting.adoc[leveloffset=+2]
|
|
|
|
include::modules/cnf-configure_for_irq_dynamic_load_balancing.adoc[leveloffset=+2]
|
|
|
|
include::modules/cnf-memory-optimization.adoc[leveloffset=+1]
|
|
|
|
include::modules/configuring-kernal-page-size.adoc[leveloffset=+2]
|
|
|
|
include::modules/cnf-configuring-huge-pages.adoc[leveloffset=+2]
|
|
|
|
include::modules/cnf-allocating-multiple-huge-page-sizes.adoc[leveloffset=+2]
|
|
|
|
[id="cnf-reducing-nic-queues-with-nto"]
|
|
== Reducing NIC queues using the Node Tuning Operator
|
|
|
|
The Node Tuning Operator facilitates reducing NIC queues for enhanced performance.
|
|
Adjustments are made using the performance profile, allowing customization of queues for different network devices.
|
|
|
|
include::modules/cnf-adjusting-nic-queues-with-the-performance-profile.adoc[leveloffset=+2]
|
|
|
|
[role="_additional-resources"]
|
|
.Additional resources
|
|
|
|
* xref:../scalability_and_performance/cnf-tuning-low-latency-nodes-with-perf-profile.adoc#cnf-create-performance-profiles[Creating a performance profile].
|
|
|
|
include::modules/cnf-verifying-queue-status.adoc[leveloffset=+2]
|
|
|
|
include::modules/cnf-logging-associated-with-adjusting-nic-queues.adoc[leveloffset=+2]
|