Skip to content

Commit 8b64ecd

Browse files
committed
TELCODOCS-1512: Adding content for new feature that enables defining shared CPUs in the performance profile
1 parent ff18e46 commit 8b64ecd

File tree

2 files changed

+30
-0
lines changed

2 files changed

+30
-0
lines changed

_topic_maps/_topic_map.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2709,6 +2709,9 @@ Topics:
27092709
- Name: Creating a performance profile
27102710
File: cnf-create-performance-profiles
27112711
Distros: openshift-origin,openshift-enterprise
2712+
- Name: Shared CPUs for peripheral workload tasks
2713+
File: cnf-shared-cpu-for-workloads
2714+
Distros: openshift-origin,openshift-enterprise
27122715
- Name: Workload partitioning
27132716
File: enabling-workload-partitioning
27142717
Distros: openshift-origin,openshift-enterprise
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
[id="cnf-shared-cpu-for-workloads"]
3+
= Shared CPUs for peripheral workload tasks
4+
include::_attributes/common-attributes.adoc[]
5+
:context: cnf-shared-cpu-for-workloads
6+
7+
toc::[]
8+
9+
Within high-performance workloads, some lightweight application tasks can occupy valuable CPU resources. For example, log printing or configuration processing can occupy an isolated core that would be better used for integral, resource-instensive workload demands. You can increase workload performance, and more efficiently use CPU resources, by moving these lightweight tasks to a set of shared CPUs.
10+
11+
You can define a set of shared CPUs by using a performance profile. Shared CPUs are a part of the kublet's `reservedSystemCpus` pool. When you enable shared CPUs, the `reservedSystemCpus` pool is internally partitioned into a `shared` CPU pool and a `reserved` CPU pool. Shared CPUs can process system housekeeping tasks and lightweight workload tasks. In contrast, reserved CPUs only process system housekeeping tasks. This ensures no added latency in system housekeeping tasks, while minor latency in peripheral workload tasks is acceptable.
12+
13+
[NOTE]
14+
====
15+
System housekeeping tasks can only run on shared CPUs when workload partitioning is disabled.
16+
====
17+
18+
19+
include::modules/cnf-about-the-profile-creator-tool.adoc[leveloffset=+1]
20+
21+
22+
23+
[id="{context}-additional-resources"]
24+
[role="_additional-resources"]
25+
== Additional resources
26+
* For more information about the `must-gather` tool,
27+
see xref:../support/gathering-cluster-data.adoc#nodes-nodes-managing[Gathering data about your cluster].

0 commit comments

Comments
 (0)