Size a host pool from CPU service demand — conditional result
29 required cores; 100 GB host state. The 32-core pool passes the screen; its CPU ceiling is about 110 requests/s.derived
| Value kind | derived — Derived values are guide calculations; their result is only as fixed as the stated inputs, scope, and method. |
|---|---|
| Scope | CPU demand = 100 requests/s × 0.20 CPU-s/request = 20 busy cores. Provision ceil(20/0.70) = 29 cores, so the 32-core pool passes and 16 cores fail. Memory = 30 × 2.0 GB + 40 GB = 100 GB, within 128 GB. The 16-core service ceiling is 16 × 0.70/0.20 = 56 requests/s; the 32-core ceiling is 32 × 0.70/0.20, about 110 requests/s. At 120 requests/s, ceil(120 × 0.20/0.70) = 35 cores: the pool must grow or the CPU work must fall. |
| As of | 2026-09 |
| Source | NVIDIA CUDA best-practices profiling guidance — method reference; guide-authored hypothetical scenario September 8, 2026. No supplier quote or test measurement. |
| Derivation | CPU demand = 100 requests/s × 0.20 CPU-s/request = 20 busy cores. Provision ceil(20/0.70) = 29 cores, so the 32-core pool passes and 16 cores fail. Memory = 30 × 2.0 GB + 40 GB = 100 GB, within 128 GB. The 16-core service ceiling is 16 × 0.70/0.20 = 56 requests/s; the 32-core ceiling is 32 × 0.70/0.20, about 110 requests/s. At 120 requests/s, ceil(120 × 0.20/0.70) = 35 cores: the pool must grow or the CPU work must fall. |
| Review | checking…review by 2027-03-08 · standard cadence |
| Recorded changes | last 2026-09-16 |
| Claim id | guide2-t29-7-8-result |
Where the guide uses it
← Full numbers register — every date-stamped figure in the guide, with revision history.