best configuration for varnish and multiple IPs and vhosts?

[Caunter, Stefan]

One varnish on one IP, that knows about all of the apache vhosts. You can run apache on 127.0.0.1 if you like. Varnish must answer externally for these websites. 

--------------------------
Sent using BlackBerry
416 561 4871

----- Original Message -----
From: varnish-misc-bounces at varnish-cache.org <varnish-misc-bounces at varnish-cache.org>
To: varnish-misc at varnish-cache.org <varnish-misc at varnish-cache.org>
Sent: Mon Jun 21 19:34:28 2010
Subject: best configuration for varnish and multiple IPs and vhosts?


I searched around for an answer to this, but wasn't able to find 
anything comprehensive, so I'll ask here.  I'm a total newbie at this 
stuff, so please let me know if I missed some obvious link.

I have a single webserver with 5 IP addresses.  Each IP has at least one 
apache-based site on it, and sometimes there are multiple on a single IP 
via NameVirtualHost.  None of the sites share any content.

What is the best varnish setup for this?  It seems there are multiple 
options:

1.  Have a single varnishd listen on all the IPs and run them all 
through a single apache port with name virtual hosts, so it's one big cache?

2.  Multiple varnish daemons, one per IP, apache listening on multiple 
ports, one per IP for the back end?

3.  Something else entirely?

I don't have a ton of memory, if that matters.  I need to use a cache 
mostly to handle spikes from being reddited and whatnot, the normal 
daily load is fine for the server.

Thanks,
Chris



_______________________________________________
varnish-misc mailing list
varnish-misc at varnish-cache.org
http://lists.varnish-cache.org/mailman/listinfo/varnish-misc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20100621/b5adcbfa/attachment-0002.html>