HCL CDP Hardware Sizing Details
This section recommends hardware configuration for HCL CDP optimized to handle 100 Transactions Per Second (TPS).
This hardware sizing guide outlines the recommended system requirements for HCL CDP designed to handle 100 Transactions Per Second (TPS).
The provided configuration has been tested to support the desired TPS, ensuring high availability, fault tolerance, and optimal resource utilization under typical workloads. This guide will help in selecting the appropriate hardware components—such as CPU, memory, storage, and network resources—required to meet performance benchmarks and provide a smooth operational experience.
Disclaimer - This guide illustrates the minimal hardware sizing requirement, based on various assumptions. This guide does not replace the need for specific Infrastructure details before the deployment. The mentioned consumptions are based on a specific scenario and hardware. Proper estimation should be done before buying the hardware. On top of the suggested hardware, appropriate buffer should be added for any expected peak/future load.
Attribute | Capacity | Allocatable |
---|---|---|
CPU | 12 | 11500m |
Ephemeral Storage | 261553132Ki | 239973624229 |
Hugepages (1Gi) | 0 | 0 |
Hugepages (2Mi) | 0 | 0 |
Memory | 32865360Ki | 31714384Ki |
Pods | 250 | 250 |
Attribute | Capacity | Allocatable |
---|---|---|
CPU | 16 | 15500m |
Ephemeral Storage | 313981932Ki | 288292006229 |
Hugepages (1Gi) | 0 | 0 |
hugepages (2Mi) | 0 | 0 |
Memory | 32864336Ki | 31713360Ki |
Pods | 250 | 250 |