You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/performanceprofile/performance_profile.md
+1
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,7 @@ CPU defines a set of CPU related features.
31
31
| reserved | Reserved defines a set of CPUs that will not be used for any container workloads initiated by kubelet. |*[CPUSet](#cpuset)| true |
32
32
| isolated | Isolated defines a set of CPUs that will be used to give to application threads the most execution time possible, which means removing as many extraneous tasks off a CPU as possible. It is important to notice the CPU manager can choose any CPU to run the workload except the reserved CPUs. In order to guarantee that your workload will run on the isolated CPU:\n 1. The union of reserved CPUs and isolated CPUs should include all online CPUs\n 2. The isolated CPUs field should be the complementary to reserved CPUs field |*[CPUSet](#cpuset)| true |
33
33
| balanceIsolated | BalanceIsolated toggles whether or not the Isolated CPU set is eligible for load balancing work loads. When this option is set to \"false\", the Isolated CPU set will be static, meaning workloads have to explicitly assign each thread to a specific cpu in order to work across multiple CPUs. Setting this to \"true\" allows workloads to be balanced across CPUs. Setting this to \"false\" offers the most predictable performance for guaranteed workloads, but it offloads the complexity of cpu load balancing to the application. Defaults to \"true\"|*bool | false |
34
+
| offlined | Offline defines a set of CPUs that will be unused and set offline |*[CPUSet](#cpuset)| true |
Copy file name to clipboardExpand all lines: manifests/20-performance-profile.crd.yaml
+3
Original file line number
Diff line number
Diff line change
@@ -370,6 +370,9 @@ spec:
370
370
isolated:
371
371
description: 'Isolated defines a set of CPUs that will be used to give to application threads the most execution time possible, which means removing as many extraneous tasks off a CPU as possible. It is important to notice the CPU manager can choose any CPU to run the workload except the reserved CPUs. In order to guarantee that your workload will run on the isolated CPU: 1. The union of reserved CPUs and isolated CPUs should include all online CPUs 2. The isolated CPUs field should be the complementary to reserved CPUs field'
372
372
type: string
373
+
offlined:
374
+
description: Offline defines a set of CPUs that will be unused and set offline
375
+
type: string
373
376
reserved:
374
377
description: Reserved defines a set of CPUs that will not be used for any container workloads initiated by kubelet.
0 commit comments