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
Linux on IBM Z and LinuxONE 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 the OperandRequest).
In the post-installation step (after creating the OperandRequest for essential services), you can change the starterset (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 the starterset (starter) profile.

Note: If you change the profile to large or medium, you cannot scale down the profile to small 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 a medium profile and another Cloud Pak specifies a medium or large (production) profile, and then you attempt to scale down to size small, the profile remains as medium. You can be able to scale down to small only if there is no other Cloud Pak with medium or large (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

Table 1. Starterset (starter) profile sizing of each service 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

Table 2. Starterset (starter) profile sizing 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

Table 3. Starterset (starter) profile sizing of each service 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

Table 4. Starterset (starter) profile sizing 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

Table 5. Starterset (starter) profile sizing of each service 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

Table 6. Starterset (starter) profile sizing 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