Cache Hit Ratio

Cache hit ratio is the percentage of requests answered directly from a cache (a hit) compared with all requests, which includes those that had to go to the origin (a miss). The formula is hits divided by hits plus misses.

Why it matters

Each hit is faster and cheaper than a miss. A higher ratio means lower origin load, lower bandwidth bills and better latency for users. CDNs usually report it in two flavors: request hit ratio and byte hit ratio, and the two can differ widely when a few large files dominate traffic.

Example

Requests in one hour:   100,000
Served from edge:        92,000  (hits)
Fetched from origin:      8,000  (misses)

Hit ratio = 92,000 / 100,000 = 92%

Many CDNs expose the result per request in a header such as X-Cache: HIT or CF-Cache-Status: HIT.

Common mistakes

• Chasing 100 percent. Personalized or rapidly changing content should not be cached.
• Varying the cache key by cookies or random query strings, which fragments the cache so most requests miss.
• Setting short TTLs on static files.
• Counting health checks and bots, which can distort the measured ratio.

Related

• CDN
• Origin shield
• Cache-Control
• HTTP caching
• टूल: CDN detector

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.