API
CDN
CDN
For static filesFor the entire site
AWS S3B2evolutionClouldFlareConcrete5CraftCs-cartDjango CMSDrupalGoogle Cloud StorageIPBIPSJoomlaKirbyMagentoPerchPrestaShopPyroCMSSocialEngineTypo3vBulletinWebasyst
Gcore pluginRocket pluginW3 Total Cache pluginWP SuperCache plugin
X-CartXenForo
Add CDN servers to ACLHTTP/2
BillingCDN resources overview
Specify an originPrivate originEnable SSL ValidationCreate a custom domain (CNAME)SSL certificatesEnable shielding (paid)Suspend a CDN resource
Configure CDN cachingSet a redirect from an originConfigure browser cachingIgnore Set Cookie or Query stringUse stale cache if origin is unavailableCache Sharding
Manage access policiesRedirect from HTTP to HTTPS
OverviewConfigure and use
Specify HTTP methodsSet SNI hostname
GZip, BrotliFetch
Custom HTTP status codeLarge files deliveryRewriteWebSockets
Add request headersActivate CORSConfigure response headersManage the Host headerIdentify a user's request protocol
Network limits
Image stack overviewEnable Image stack
Convert to WebP or AVIFChange qualityCropResize
Troubleshooting
Streaming via CDN (for paid tariffs)Geobalancer (for paid tariffs)
Create a ruleCreate a template for rulesAvoid indexing
Origin group
SSL overviewOwn SSL certificateLet's Encrypt certificate
PurgePrefetch
Raw Logs (paid)Log Viewer (free)
Reports
Grafana reportsTerraform
Error status codesContent unavailabilityLow cache hit ratioLow content delivery speedAttaching or issuing an SSL certificate3xx codes4xx codes5xx codes
Support API
Chosen image
Home/CDN/Troubleshooting/Low cache hit ratio

Cache percentage is low: how to solve the issue

Cached traffic is traffic that is delivered from CDN edge’s cache without request to the origin server. 

You may track the Cache Hit Ratio percentage on the Report tab. 

Cache Hit Ratio depends on the number of requests and the amount of traffic. If you have noticed that the cache hit ratio is 60% or less: 

  1. Make sure that your website or application is integrated with CDN successfully: the static content is delivered through a custom domain, the custom domain is set up correctly. 
  2. Make sure that more than 2 days have passed since you have started to use CDN. 
  3. Deliver more content through CDN, if possible.

 

If you already set up CDN delivery for all possible static content, but the cache hit ratio remains low, revise the CDN resource’s cache settings: 

CDN Caching option

CDN Caching option

Check if this option is added and activated. If you use this option with Origin controlled parameter make sure that origin settings are suitable for caching.

CDN caches according to Cache-Control headers from your origin. 

Note: Cache-control directives that are not suitable for CDN:  no-cache, no-store, private, max-age=0 

Query-String and Set-Cookies options

Query-String and Set-Cookies options

CDN caches content with different query-strings and Set-Cookie headers separately by default If you have such content on your website or application, we recommend you to use Ignore Query-String and Ignore Set-Cookies options for the CDN-resource. It will help to decrease the number of requests from CDN to the origin server and increase the Cache hit ratio. 

Large Files Delivery Optimization

Large Files Delivery Optimization

Use the Large Files Delivery Optimization option for the large content caching. You may know more about the option from the article. 

If you add any parameters (for example, a unique signature for users) to the URL, but not as a query string (http://cdn.example.com/image.jpg?id=1), it requires custom caching keys set up. 

Contact technical Support for manual settings and describe the URL scheme: which parts should be cached and which – should not.

Was this article helpful?

Not a Gcore user yet?

Learn more about our next-gen CDN

Go to the product page
Edit on GitHub