Estimate origin Mbps, monthly TB and log storage from RPS, response size, static ratio, CDN offload, TLS overhead and logs.
$ peak RPS x response size $ static x CDN-offload $ + protocol overhead $ output: origin Mbps / TB / logs
RPS alone does not determine network capacity. Response size and CDN offload are equally important.
This tool produces a starting estimate for capacity planning; validate production decisions with load tests and real monitoring data.
Change the inputs and calculate again.
Dynamic HTML/API is usually computed at origin; cached static assets can be served by CDN.
TLS, TCP/IP, HTTP headers and retransmissions add bytes beyond payload.
High RPS can create large access, application and audit logs; plan rotation and retention.
Open connections alone do not define Mbps; message size and frequency matter.
It depends on response size; 100 KB payload is roughly an 800 Mbps payload rate before overhead.
It can remove cached static requests from origin.
There is no single fixed rate; use measured values.
Choose from security, legal and operational requirements, then budget storage.
Share your workload, traffic profile and growth target so we can determine the appropriate VPS or GPU server class.