[wp-hackers] Varnish and WordPress

[Demitrious S. Kelly]

yes, but there are some gotchas

A) you can only do regex invalidation through the command line client, 
which is not so useful if you are running varnish on a seperate server 
from your wordpress install. 

B) invalidations through VCL are one for one, .* does not work this way

C) varnish cannot purge just for a specific host.  It's all hosts or 
nothing.

D) in our tests we found the telnet interface was... less than reliable.

So for large sites with scaled needs varnish is less attractive than it 
could be.

Joseph Scott wrote:
>
> On Aug 2, 2007, at 1:25 PM, Demitrious S. Kelly wrote:
>
>> To the best of my knowledge varnish does not work as a content
>> accelerator with wordpress. Because of the flow of information through
>> wordpress blogs (last-in-first-out) the entire blog (or at least very
>> large chunks of it) would need to be invalidated for every
>> add/edit/delete action. Because of the mutable URI structure of
>> wordpress it difficult to generate a complete list of URI/URLs that
>> might have changed because of a given action. This, mixed with the fact
>> that (afaik) varnish does not allow wild card invalidations, only
>> specific URI/URL invalidations, makes varnish less than ideal as a
>> content accelerator for WP. We're working on a project called WPCP which
>> should alleviate this problem for very large shops for whom wp-cache is
>> too unruly. For now, wp-cache is still your safest bet.
>
>
> Purging (invalidation) is one of the nice features of Varnish.  The 
> FAQ (http://varnish.projects.linpro.no/wiki/FAQ) shows how to purge 
> using the command line tool and via HTTP.  They use regexs so you can 
> purge as much or as little of the cache as you want.
>
>
> -- 
> Joseph Scott
> http://joseph.randomnetworks.com/
>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers