This article will review some of the most frequent terms related to CDN and caching. Understanding those terms is really important to check the effectiveness of content delivery and know how to check if the "Invalidation" process works.
| What is a cache-HIT? | What is a cache-MISS? |
|
A "cache-HIT" happens when a file is requested from a cache which can meet the request. For instance, if a user visits a webpage that's supposed to present a picture of a boat, the browser may request the webpage's CDN for this image. If the CDN has a copy of the photograph in its storage, the request results in a cache hit and the picture is sent to the user's browser.
|
A "cache-MISS" is when the cache does not contain the demanded content. If a copy of the boat picture is not currently in the CDN cache, this request results in a cache miss, and the request is moved along to the origin server for the original picture. The CDN server will cache the photo once the origin server responds so that additional requests for it will result in a cache hit.
|
Finally, what is the Cache-HIT Ratio?
The cache-HIT Ratio measures how many content requests a cache is able to successfully fill compared to the total number of requests it receives. A content delivery network provides a type of cache, and a high-performing CDN will have a high cache hit ratio in most cases, but this is not all you need to monitor and consider.
If you have any questions or issues, please feel free to contact our Software Engineer and mention the following details:
- Token
- Short description of the issue (including URLs, screenshots, short video if available)
- Steps to reproduce the issue.
Comments
Please sign in to leave a comment.