Adamant Solutions

API capacity sizing calculator

Turn peak traffic and latency into requests in flight, bandwidth, backend connections and a gateway node count with headroom. Runs in your browser; we only count anonymous visits.

How to use this tool

  1. Enter the peak requests per second, or the daily volume and how much busier the peak is than the average.
  2. Enter the average latency your clients actually see and the typical payload sizes.
  3. Enter the capacity of one node that you measured with a load test at that latency, and the utilisation you want at peak (60 % is a common starting point).

Example

500 requests/s at 200 ms means 100 requests in flight (Little's law: concurrency = rate × time). With 300 requests/s per node and a 60 % target, 3 nodes carry the peak and a 4th gives N+1 redundancy, so losing a node still leaves the others under 100 %.

Limits

This is arithmetic, not a benchmark. The per-node capacity must come from your own load test of your own policies, TLS settings and payloads; products differ widely and we do not publish vendor numbers. It ignores bursts shorter than a second, retries, cache hit ratios and warm-up. Treat the output as a starting estimate to check with a test.

Privacy and security of what you enter

The numbers never leave your browser. See the privacy notice.

Need a capacity review before launch?

We review gateway topology, timeouts, thread pools and rate limits. See the services, or try the HTTP request tester.

Message us on LinkedIn

Privacy and cookies