Hosting

Cache Hit Ratio Calculator

Calculate cache hit ratio from cache hits and total requests.

Last reviewed: April 30, 2026Free toolMethodology

Cache Hit Ratio Calculator

These fields start with sample inputs. Keep them or replace them, then run the tool to show a fresh result.

Number fields accept plain values and common formatted input such as 250000, 250,000, or 1,234.56.

Result

Calculating the sample result.

Why it matters

Cache hit ratio directly affects origin load, latency, and infrastructure cost in websites and APIs.

When to use

  • Reviewing CDN or application cache performance
  • Estimating origin offload
  • Checking whether a caching change improved efficiency

Inputs & Outputs

Inputs

  • Cache hits are the requests served from cache.
  • Total requests are the full request volume across the same period.

Outputs

  • Hit ratio shows the share of requests served from cache.
  • Origin requests show how much traffic still reached the backing system.

Hit-ratio formula

Divide cache hits by total requests and convert the result into a percentage.

Cache hit ratio = cache hits / total requests

Worked example

1

CDN review

A service serves 9.2 million requests from cache out of 10 million total requests.

Inputs

  • Cache hits: 9,200,000
  • Total requests: 10,000,000

Steps

  • Hit ratio = 9,200,000 / 10,000,000 = 92%

Result

  • Cache hit ratio is 92%, leaving 800,000 origin requests.

Edge cases & caveats

  • A high hit ratio is not the only performance goal; stale content risk matters too.
  • Different route mixes can change the ratio even without a config change.

Frequently Asked Questions

Is a high cache hit ratio always good?

Usually helpful for cost and latency, but only if cache freshness and correctness remain acceptable.

Why does origin offload matter?

Because lower origin traffic can reduce server load, egress cost, and response-time variability.

Keep going