Check whether an attribution pipeline has enough throughput for peak event traffic. Compare required events per second with available worker capacity, utilization, spare throughput, and the minimum worker count needed at a chosen safety target.
Use sustained benchmark throughput rather than a short burst maximum.
Use the main result together with the supporting bounds, counts, or capacity figures. The estimate is only as reliable as the input definitions, sampling process, and operating assumptions.
Capacity estimates assume workers scale similarly and the per-worker benchmark includes normal I/O, joins, retries, and model evaluation.
12 units at 1,800 requests per second provide 21,600 requests per second. Demand of 18,000 uses 83.3% of raw capacity.
Total capacity equals the number of workers or instances multiplied by measured throughput per worker or instance.
Operating below theoretical maximum leaves headroom for bursts, retries, uneven load, maintenance, and performance variation.
Use a credible peak demand for sizing. Average traffic can materially understate the resources needed during busy periods.
No. It estimates throughput capacity. Validate p95 and p99 latency separately under realistic load.
Not always. Shared databases, queues, networks, coordination, and cache behavior can reduce scaling efficiency.
| Input | Unit |
|---|---|
| Peak demand | Requests or events per second |
| Unit throughput | Sustained requests or events per second |
| Target utilization | Planned operating ceiling |