Lots of configs

AD straightflush at gmail.com
Sun Mar 6 23:39:41 CET 2011


 what is the best way to run an instance of varnish that may need different
vcl configurations for each hostname.  This could end up being 100-500
includes to map to each hostname and then a long if/then block based on the
hostname.  Is there a more scalable way to deal with this?  We have been
toying with running one large varnish instance with tons of includes or
possibly running multiple instances of varnish (with the config broken up)
or spreading the load across different clusters (kind of like sharding)
based on hostname to keep the configuration simple.

 Any best practices here?  Are there any notes on the performance impact of
the size of the VCL or the amount of if/then statements in vcl_recv to
process a unique call function ?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20110306/870548f3/attachment-0003.html>

More information about the varnish-misc mailing list