mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 09:46:53 +01:00
29 lines
1.7 KiB
Plaintext
29 lines
1.7 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// microshift_configuring/microshift_low_latency/microshift-low-latency.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="microshift-low-latency-concept_{context}"]
|
|
= Lowering latency in {microshift-short} applications
|
|
|
|
Latency is defined as the time from an event to the response to that event. You can use low latency configurations and tuning in a {microshift-short} cluster running in an operational or software-defined control system where an edge device has to respond quickly to an external event. You can fully optimize low latency performance by combining {microshift-short} configurations with operating system tuning and workload partitioning.
|
|
|
|
[IMPORTANT]
|
|
====
|
|
The CPU set for management applications, such as the {microshift-short} service, OVS, CRI-O, {microshift-short} pods, and isolated cores, must contain all-online CPUs.
|
|
====
|
|
|
|
[id="microshift-low-latency-workflow_{context}"]
|
|
== Workflow for configuring low latency for {microshift-short} applications
|
|
To configure low latency for applications running in a {microshift-short} cluster, you must complete the following tasks:
|
|
|
|
Required::
|
|
* Install the `microshift-low-latency` RPM.
|
|
* Configure workload partitioning.
|
|
* Configure the `kubelet` section of the `config.yaml` file in the `/etc/microshift/` directory.
|
|
* Configure and activate a TuneD profile. TuneD is a {op-system-base-full} service that monitors the host system and optimizes performance under certain workloads.
|
|
* Restart the host.
|
|
|
|
Optional::
|
|
* If you are using the x86_64 architecture, you can install link:https://docs.redhat.com/en/documentation/red_hat_enterprise_linux_for_real_time/9[Red Hat Enterprise Linux for Real Time 9].
|