Customizing resources in DataStage

Important: IBM Cloud Pak® for Data Version 4.7 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.7 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.

An administrator or other user with appropriate permissions can customize instances of the DataStage® service.

A parallel engine (PX) DataStage instance is the runtime environment that DataStage jobs run on. The default instance is provisioned under the administrator account, so only users with administration permissions can view or edit the default instance. Other instances can be viewed or edited by users whose role has the correct permissions to do so. Administrators can create new roles with permissions as needed.

Each PX instance has its own conductor and compute pods to ensure the DataStage workloads are separate. The size of an instance, the number of pods, and the allocation of resources such as memory can be customized by editing the PX runtime custom resource (CR).

Default t-shirt sizes for PX runtime

Small

2 compute pods: 3 vCPU and 12 GB RAM (6 VPC)

1 conductor pod: 1 vCPU and 4 GB RAM

Medium

2 compute pods: 6 vCPU and 24 GB RAM (12 VPC)

1 conductor pod: 2 vCPU and 4 GB RAM

Large

3 compute pods: 8 vCPU and 32 GB RAM (24 VPC)

1 conductor pod: 4 vCPU and 4 GB RAM