Hit ratio dropped significantly after recent upgrades

Dridi Boukelmoune dridi at varni.sh
Tue Dec 13 16:42:01 CET 2016


On Tue, Dec 13, 2016 at 4:20 PM, Justin Lloyd <justinl at arena.net> wrote:
> That's really the crux of my problem, as I tried to summarize in my last big email though it was longer than it probably should have been. Is it possible to determine from varnishlog whether/which requests are being missed and fetched but not cached?

There are more things you can see with varnishlog like hashes for
instance, but you could start by logging markers in your VCL to see
which branches you are taking.

Example:

    if (beresp.ttl <= 0s) {
        std.log("negative ttl");
        set beresp.uncacheable = true;
        return (deliver);
    }

And do the same for all branches, and see which code is executed.

> I get the feeling that this will turn out to be either something very simple in the Varnish and/or MediaWiki configuration or else a bug somewhere, though I'd lean towards the former as being more likely.

If you can reproduce it in lab conditions where you are the only user,
look for a transaction containing:

    - VCL_return hash
    - VCL_call HASH
    - VCL_return lookup
    - VCL_call PASS

And then look for the previous transaction on the same resource.

Dridi



More information about the varnish-misc mailing list