I currently analyze varnish hit rate like this
http://d.pr/i/RswMeL
<https://mailtrack.io/trace/link/2a6a624a67c72c8b5fabc0f3ba4f44c93eb39964?url=http%3A%2F%2Fd.pr%2Fi%2FRswMeL&userId=74734&signature=167bba0ff7e3ed50>
While this is good, a major part of the request the server services is
non-cacheable. This brings down the hit rate drastically.
How can I modify this such that I count only requests that are candidates
for caching and calculate the rate? Which varnishstat metric should I be
looking?
- Quintin
http://d.pr/i/RswMeL
<https://mailtrack.io/trace/link/2a6a624a67c72c8b5fabc0f3ba4f44c93eb39964?url=http%3A%2F%2Fd.pr%2Fi%2FRswMeL&userId=74734&signature=167bba0ff7e3ed50>
While this is good, a major part of the request the server services is
non-cacheable. This brings down the hit rate drastically.
How can I modify this such that I count only requests that are candidates
for caching and calculate the rate? Which varnishstat metric should I be
looking?
- Quintin