mass purge causes high load?

[Dag-Erling Smørgrav]

[resent to varnish-misc]

Sascha Ottolski <ottolski at web.de> writes:
> Dag-Erling Smørgrav <des at linpro.no> writes:
> > If you know the exact URL to purge, use an HTTP PURGE (see VCL code
> > examples in the vcl man page)
> I'm aware of this, but had expected that the semantic of both method
> would be identical. Especially as I did not pass regular expresssions,
> but the complete URLs. Well, at least that's what I thought :-)

No, the semantics are completely different.  With HTTP PURGE, you do a
direct cache lookup, and set the object's TTL to 0 if it exists.  With
url.purge, you add an entry to a ban list, and every time an object is
looked up in the cache, it is checked against all ban list entries that
have arrived since the last time.  This is the only way to implement
regexp purging efficiently.

DES
-- 
Dag-Erling Smørgrav
Senior Software Developer
Linpro AS - www.linpro.no