Caching efficiency, VCL
Eirik Øverby
ltning at anduin.net
Thu Sep 21 08:32:11 CEST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
installed Varnish during the presentation yesterday, and was playing
with it for most of the evening (together with Marcus, who has
already reared his head on the -dev list). Given the nature of the
site we're trying to serve, there's not much that can be cached
unless we do some serious customizations on the VCL side. That,
combined with some adjustments of the site code, and we should see
some pretty good improvements.
Questions:
- - Others on this list have asked for VCL documentation. I seel the
same.
- - There's also some lack in the documentation of (runtime) parameters
listed in the varnishd man page.
- - Can I control access to the management interface through VCL?
- - Due to the fact that webserver and varnish are currently running on
the same box, I am using a pf ruleset like the following:
no rdr on $int_if proto tcp from $my_ip to $my_ip port 80
rdr on $int_if proto tcp from any to $my_ip port 80 -> $my_ip port 8080
Is this going to limit my performance in any significant way? Given
that I'm running on hardware comparable to what the devs have been
testing on, and the site I'm serving sees only a tiny fraction of the
traffic, I wouldn't think so.
- - The cmdline allows me to specify a minimum ttl for objects -- I'm
missing a way to specify max ttl. Is this something I could do in
VCL, and in that case, why is there an option for the minimum ttl?
I guess that's it for now. Hoping to get a grip of this beast soon!
Thanks,
/Eirik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFFEjHsDRlfnc8VQWcRAqgkAJ9Id6zN9xcaulN8Q27bJIuhL1U95wCgmwrj
gC4fwotnyxTrN6ZjRkKP49g=
=oyBw
-----END PGP SIGNATURE-----
More information about the varnish-misc
mailing list