Hardware requirements of starterset (starter)
profile
Review the following tables if you are deploying a starterset (starter)
profile of foundational services.
- Linux® x86_64 clusters
- Linux® on Power® (ppc64le) clusters
-
Table 1 provides the hardware requirement of each individual service, excluding the hardware requirement of its dependencies.
-
Table 2 provides the hardware requirement of individual services, including the hardware requirement of their dependencies.
See the following notes:
-
You can switch between
starterset (starter)
,small
,medium
,large (production)
profiles before the installation of foundational services (before creating theOperandRequest
). -
In the post-installation step (after creating the
OperandRequest
for essential services), you can change thestarterset (starter)
profile to small, medium, and large (production) profiles. However, once you change your profile to small, medium, or large (production), you cannot roll back to thestarterset (starter)
profile.Note: If you change the profile to
large
ormedium
, you cannot scale down the profile tosmall
after installation. However, scaling down a profile can be done only if no other Cloud Pak has requested for a larger (production) size. For example, if you install with amedium
profile and another Cloud Pak specifies amedium
orlarge (production)
profile, and then you attempt to scale down to sizesmall
, the profile remains asmedium
. You can be able to scale down tosmall
only if there is no other Cloud Pak withmedium
orlarge (production)
size. You can be able to scale down to a starterset (starter) profile with 3 MongoDB replicasets.
-
For capacity planning, consider the CPU request and memory request.
- The CPU request is the minimum number of cores that must be available when a service is created.
- The memory request is the minimum amount of memory that must be available when a service is created.
-
To determine the total CPU and memory requirement for all services, see Hardware requirements and recommendations for foundational services.
Linux® x86_64 clusters
Hardware requirements of individual services for Linux® x86_64 clusters
Service Name | Replica | CPU Request (cores) | CPU Limit (cores) | Memory Request (GB) | Memory Limit (GB) |
---|---|---|---|---|---|
IM | 1 | 1.5 | 3 | 1.2 | 2.2 |
MongoDB | 1 | 0.5 | 1 | 0.7 | 0.7 |
Common Web UI | 1 | 0.2 | 1 | 0.3 | 0.5 |
Hardware requirements of individual services with dependencies for Linux® x86_64 clusters
Service Name | Dependencies | CPU Request (cores) | CPU Limit (cores) | Memory Request (GB) | Memory Limit (GB) |
---|---|---|---|---|---|
IM | MongoDB, Common Web UI | 2.2 | 5 | 2.2 | 3.4 |
Linux® on Power® (ppc64le) clusters
Hardware requirements of individual services for Linux® on Power® (ppc64le) clusters
Service Name | Replica | CPU Request (cores) | CPU Limit (cores) | Memory Request (GB) | Memory Limit (GB) |
---|---|---|---|---|---|
IM | 1 | 0.3 | 4 | 0.8 | 1.6 |
MongoDB | 1 | 0.5 | 1 | 0.7 | 0.7 |
Common Web UI | 1 | 0.2 | 1 | 0.3 | 0.5 |
Hardware requirements of individual services with dependencies for Linux® on Power® (ppc64le) clusters
Service Name | Dependencies | CPU Request (cores) | CPU Limit (cores) | Memory Request (GB) | Memory Limit (GB) |
---|---|---|---|---|---|
IM | MongoDB, Common Web UI | 1 | 6 | 1.8 | 2.8 |
Linux® on IBM® Z and LinuxONE clusters
Hardware requirements of individual services for Linux® on IBM® Z and LinuxONE clusters
Service Name | Replica | CPU Request (cores) | CPU Limit (cores) | Memory Request (GB) | Memory Limit (GB) |
---|---|---|---|---|---|
IM | 1 | 0.3 | 3 | 0.8 | 1.2 |
MongoDB | 1 | 0.5 | 1 | 0.7 | 0.7 |
Common Web UI | 1 | 0.2 | 1 | 0.3 | 0.5 |
Hardware requirements of individual services with dependencies for Linux® on IBM® Z and LinuxONE clusters
Service Name | Dependencies | CPU Request (cores) | CPU Limit (cores) | Memory Request (GB) | Memory Limit (GB) |
---|---|---|---|---|---|
IM | MongoDB, Common Web UI | 1 | 5 | 1.8 | 2.4 |