Damon Snyder damon at huddler-inc.com
Fri Feb 10 18:36:26 CET 2012

See some suggestions inline below. Hope this helps get you started.

Server configuration (planned):
> Intel(R) Xeon(R) CPU X5460 @ 3.16GHz, 3 cores, 1.75 GB of RAM, Max of 3 GB
> burstable
> Linux 2.6.32-042stab044.17 on i686 (CenOS 6.2)

This is probably overkill. Varnish/nginx are not that cpu intensive. You
are probably fine with that amount of memory to get started.

> Questions:
> How can I tell Varnish to enable cache on certain url and let pass cookies
> on others/rest of the site?

Check out the docs on how to cache/not specific urls. Its pretty straight
forward. See https://www.varnish-cache.org/docs/3.0/tutorial/vcl.html. One
thing you want to do from the start is add a HIT/MISS header for debugging
your configuration. See

> Having 500.000 visits/month what's the best practice for cache purge?

Purge whenever you have new content. The purging is lazy, so you don't have
to worry about purging being costly or effecting the operation.

> How can i configure varnish and nginx, one serving cached pages and the
> other (nginx) serving static content like images ON THE SAME MACHINE. I
> have 2 spare IP address.

This is pretty common. You can have nginx serve maint pages and static
content then proxy_pass to varnish for the content you want cached.

> I have HyperCache plugin for Wordpress, it generates static files of the
> site and sends it to nginx to serve. APC also do its work. Should I disable
> HyperCache and let Varnish take care of the PHP content?
> More on HyperCache on http://www.satollo.net/**plugins/hyper-cache<http://www.satollo.net/plugins/hyper-cache>

Varnish is good at what it does. I would lean on varnish first so long as
you can get the purging hooked in to wordpress. Since your content is
updated on a schedule, you could probably purge by hand when new content is

Hope this helps,

> ______________________________**_________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/**lists/mailman/listinfo/**varnish-misc<https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20120210/f2abb676/attachment.html>

More information about the varnish-misc mailing list