mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 00:48:01 +01:00
17793ab106
This commit modifies the tested cluster maximums for OpenShift 4.4 and 4.5 releases to match with the documented environment information. Tested maximums reported for major releases ( 3.x and 4.x ) still stay the same.
98 lines
2.8 KiB
Plaintext
98 lines
2.8 KiB
Plaintext
// Module included in the following assemblies:
|
||
//
|
||
// * scalability_and_performance/planning-your-environment-according-to-object-maximums.adoc
|
||
|
||
[id="cluster-maximums_{context}"]
|
||
= {product-title} tested cluster maximums
|
||
|
||
[options="header",cols="6*"]
|
||
|===
|
||
| Maximum type |4.1 and 4.2 tested maximum |4.3 tested maximum |4.4 tested maximum |4.5 tested maximum |4.6 tested maximum
|
||
|
||
| Number of Nodes
|
||
| 2,000
|
||
| 2,000
|
||
| 250
|
||
| 500
|
||
| 2,000
|
||
|
||
| Number of Pods footnoteref:[numberofpods,The Pod count displayed here is the number of test Pods. The actual number of Pods depends on the application’s memory, CPU, and storage requirements.]
|
||
| 150,000
|
||
| 150,000
|
||
| 62,500
|
||
| 62,500
|
||
| 150,000
|
||
|
||
| Number of Pods per node
|
||
| 250
|
||
| 500
|
||
| 500
|
||
| 500
|
||
| 500
|
||
|
||
| Number of Pods per core
|
||
| There is no default value.
|
||
| There is no default value.
|
||
| There is no default value.
|
||
| There is no default value.
|
||
| There is no default value.
|
||
|
||
| Number of Namespaces footnoteref:[numberofnamepaces, When there are a large number of active projects, etcd might suffer from poor performance if the keyspace grows excessively large and exceeds the space quota. Periodic maintenance of etcd, including defragmentaion, is highly recommended to free etcd storage.]
|
||
| 10,000
|
||
| 10,000
|
||
| 10,000
|
||
| 10,000
|
||
| 10,000
|
||
|
||
| Number of Builds
|
||
| 10,000 (Default pod RAM 512 Mi) - Pipeline Strategy
|
||
| 10,000 (Default pod RAM 512 Mi) - Source-to-Image (S2I) build strategy
|
||
| 10,000 (Default pod RAM 512 Mi) - Source-to-Image (S2I) build strategy
|
||
| 10,000 (Default pod RAM 512 Mi) - Source-to-Image (S2I) build strategy
|
||
| 10,000 (Default pod RAM 512 Mi) - Source-to-Image (S2I) build strategy
|
||
|
||
| Number of Pods per Namespace footnoteref:[objectpernamespace,There are
|
||
a number of control loops in the system that must iterate over all objects
|
||
in a given namespace as a reaction to some changes in state. Having a large
|
||
number of objects of a given type in a single namespace can make those loops
|
||
expensive and slow down processing given state changes. The limit assumes that
|
||
the system has enough CPU, memory, and disk to satisfy the application requirements.]
|
||
| 25,000
|
||
| 25,000
|
||
| 25,000
|
||
| 25,000
|
||
| 25,000
|
||
|
||
| Number of Services footnoteref:[servicesandendpoints,Each service port and each service back-end has a corresponding entry in iptables. The number of back-ends of a given service impact the size of the endpoints objects, which impacts the size of data that is being sent all over the system.]
|
||
| 10,000
|
||
| 10,000
|
||
| 10,000
|
||
| 10,000
|
||
| 10,000
|
||
|
||
| Number of Services per Namespace
|
||
| 5,000
|
||
| 5,000
|
||
| 5,000
|
||
| 5,000
|
||
| 5,000
|
||
|
||
| Number of Back-ends per Service
|
||
| 5,000
|
||
| 5,000
|
||
| 5,000
|
||
| 5,000
|
||
| 5,000
|
||
|
||
| Number of Deployments per Namespace footnoteref:[objectpernamespace]
|
||
| 2,000
|
||
| 2,000
|
||
| 2,000
|
||
| 2,000
|
||
| 2,000
|
||
|
||
|===
|
||
|
||
In {product-title} {product-version}, half of a CPU core (500 millicore) is
|
||
reserved by the system compared to {product-title} 3.11 and previous versions.
|