Skip to content

TELCODOCS-2272-RN422 NUMA-aware scheduler 500 node scalability release note #110693

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kquinn1204 wants to merge 3 commits into
base: enterprise-4.22
Choose a base branch
from
+6 −0
Open

TELCODOCS-2272-RN422 NUMA-aware scheduler 500 node scalability release note #110693

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
be006fe
TELCODOCS-2272-RN422 NUMA-aware scheduler 500 node scalability releas…
kquinn1204 Apr 23, 2026
ae6e8d9
TELCODOCS-2272-RN422-numa Fix release note format and xref
kquinn1204 Apr 23, 2026
29f5ad2
updates to RN to keep it simple
kquinn1204 Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions modules/rn-ocp-release-notes-new-features.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -184,6 +184,12 @@ Detailed information.
[id="ocp-release-notes-scale-and-perform_{context}"]
== Scalability and performance

// TELCODOCS-2272
NUMA-aware scheduler supports clusters with up to 500 nodes::
+
With this release, you can scale the NUMA-aware secondary scheduler to support clusters with up to 500 nodes. The scheduler defaults to a `Burstable` quality of service (QoS) profile, which reduces baseline resource consumption while allowing the scheduler to scale up during peak loads.
+
For more information, see xref:../scalability_and_performance/cnf-numa-aware-scheduling.adoc#cnf-topology-aware-scheduler-scalability_numa-aware[Topology-aware scheduler scalability].

// [id="ocp-release-notes-support-sigstore_{context}"]
// == Support for sigstore bring your own PKI (BYOPKI) image validation
Expand Down