The Varnish Cache project provides some high level instructions on improving cache hit rate.
The following describes the work flow with section.io metrics and development processes to achieve optimal cache hit ratios.
- Review section.io Varnish Cache metrics
- Review http logs
- Make changes to VCL locally
- Confirm change has been effective -> Logs
- Promote changes to Production
- Confirm change has been effective -> Metrics
- Rinse and repeat
Your section.io Varnish Cache metrics provide an overview of cache hit ratios for all asset types in addition to cache hit ratios by type.
You can use these metrics to identify an object type for which you would like the cache hit ratio to be improved.
Use the Kibana logs to review the HTTP requests. For more information about these logs please check out the docs here.
Modify your local VCL file. Save and fire the requests at your local instance. See Local Development.
Review logs again to confirm a change in the cache hit behavior for the target assets.
If required you can test the application locally to confirm the VCL changes have not affected the functionality of the application adversely for users.
Sync your section.io repo with production and confirm cache hit rates are improving by reviewing your metrics.
Until you hit a desirable cache hit rate across the site.
Awesome! Steps 5 through 7 are meant to be an iterative process. Focus on big wins first using your metrics evaluation. Then after you’ve improved those areas, you can focus on other areas to fine tune.
section.io is here to help with setup and can be reached by emailing email@example.com. If you want help with configuration you can ask us about consulting engagements, and if you want a fully managed service please contact us for a quote.