hit rate on a staging website
andrew.langhorn at digital.cabinet-office.gov.uk
Mon Dec 1 08:19:06 CET 2014
I think that depends on all sorts of factors, especially including what
your VCL says to Varnish to consider a hit, miss or pass.
Let's assume you used defaults, though. Half of the content on your staging
site is being returned by Varnish with no backend calls required. That
seems a good starting point to me. If it's a development site, then things
will be changing a lot all the time I assume and you won't want some stuff
(like auth) cached. If it's an ecommerce site, you'll want even less cached
- eg checkout etc.
Instead of caring about your hit rate, I'd care more about your miss rate.
These are the requests being sent to origin to respond via Varnish. And
these are the requests that take up resources on your origin. Try to keep
getting that lower, and you should be fine.
By the way - have you tried varnishstat? It's a good way to get all these
stats out of Varnish.
On Monday, 1 December 2014, Tim Dunphy <bluethundr at gmail.com> wrote:
> Hey guys,
> We've setup some monitoring on a staging version of a production web site
> at work. It looks like we're getting about a .50 (or 50%) hit rate on the
> staging site. We haven't monitored the production site for varnish hit
> rates yet. We're using a Nagios check written in perl for that.
> But if it's possible to think of this in general terms, what I'd like to
> know is if you think that .50 is a respectable hit rate for a php/drupal
> site that's basically not in production, and the traffic it encounters is
> synthetic. Basically it's tested out by the developers and load tests are
> run against it using load generators as you might expect.
> And of course, some of the site content is dynamic and not meant to be
> Here's how it's broken down:
> cache_hit 222628
> cache_miss 220674
> Here's we how calculate cache hit percent
> cache_hit_percent = ( cache_hit / ( cache_hit + cache_miss ) ) * 100
> So all I want to know from the more experienced varnish guys is, would you
> consider this an acceptable cache hit rate given my situation?
> GPG me!!
> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the varnish-misc