Skip to content
Calcrivo

Web Proxy Capacity Calculator

Size a secure web gateway cluster: appliances required with N+1 sparing, users per node and access-log storage.

Inputs

users
req/h
×
req/s
appliances

1 gives N+1; 2 gives N+2 for maintenance during a failure.

bytes
days

Appliances Required

2

Active Appliances

1

Peak Request Rate

3,666.7req/s

Utilisation of Active Nodes

61.1%

Users per Appliance

10,000

Access Log Storage

4.13 TiB

Step by step

  1. Values used

    Users to serve = 20,000 users; Requests per user per hour = 300 req/h; Peak-to-average factor = 2.20 ×; Rated requests per second per appliance = 6,000 req/s; Spare appliances for redundancy = 1 appliances; Access log bytes per request = 350 bytes; Log retention = 90 days

  2. Web Proxy Capacity

    active appliances = ceil(peak rps ÷ rated rps); total = active + spares; log storage = requests per day × bytes per request × retention days.

  3. Appliances Required

    = 2

  4. Active Appliances

    = 1

  5. Peak Request Rate

    = 3,666.7 req/s

  6. Utilisation of Active Nodes

    = 61.1

  7. Users per Appliance

    = 10,000

  8. Access Log Storage

    = 4,536,000,000,000.00

How it works

Divide the peak request rate by the rated per-appliance rate and round up for the active node count, then add spares so a failure or maintenance window does not push the survivors past capacity. Access logs are sized independently: every request writes a line, and at proxy volumes that dominates your SIEM ingest bill. Web proxy log volume is routinely the largest single feed into a SIEM, so discovering the storage cost after deployment turns a security control into a budget problem.

Formula

Web Proxy Capacity

active appliances = ceil(peak rps ÷ rated rps); total = active + spares; log storage = requests per day × bytes per request × retention days.

rated rps
Vendor-rated request rate per appliance with your policy enabled
spares
Extra nodes so a failure does not reduce capacity below peak

Frequently Asked Questions

How is Web Proxy Capacity calculated?

active appliances = ceil(peak rps ÷ rated rps); total = active + spares; log storage = requests per day × bytes per request × retention days. Divide the peak request rate by the rated per-appliance rate and round up for the active node count, then add spares so a failure or maintenance window does not push the survivors past capacity. Access logs are sized independently: every request writes a line, and at proxy volumes that dominates your SIEM ingest bill.

Why does Web Proxy Capacity matter?

Web proxy log volume is routinely the largest single feed into a SIEM, so discovering the storage cost after deployment turns a security control into a budget problem.

What values do I need to enter?

This calculator takes 7 inputs: Users to serve, Requests per user per hour, Peak-to-average factor, Rated requests per second per appliance, Spare appliances for redundancy, Access log bytes per request, Log retention. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Should the rated rps come from the datasheet?

Only as a starting point. Datasheet figures assume minimal policy: no TLS interception, no sandboxing, no data-loss inspection and a small category database. With full TLS interception enabled, expect a third or less of the rated figure, so validate against a proof of concept with your real policy.

You might also need