cache empties itself?

Michael S. Fischer michael at
Tue Apr 8 02:22:42 CEST 2008

On Fri, Apr 4, 2008 at 3:31 PM, Ricardo Newbery <ric at> wrote:

> > > Again, "static" content isn't only the stuff that is served from
> > > filesystems in the classic static web server scenario.  There are plenty
> of
> > > "dynamic" applications that process content from database -- applying
> skins
> > > and compositing multiple elements into a single page while filtering
> every
> > > element or otherwise applying special processing based on a user's
> access
> > > privileges.  An example of this is a dynamic content management system
> like
> > > Plone or Drupal.  In many cases, these "dynamic" responses are fairly
> > > "static" for some period of time but there is still a definite
> performance
> > > hit, especially under load

>  In any case, both of these examples, Plone and Drupal, can indeed cache the
> output "locally" but that is still not as fast as placing a dedicated cache
> server in front.  It's almost always faster to have a dedicated
> single-purpose process do something instead of cranking up the hefty
> machinery for requests that can be adequately served by the lighter process.

Sure, but this is also the sort of content that can be cached back
upstream using ordinary HTTP headers.

Still waiting for that compelling case that requires independent cache


More information about the varnish-misc mailing list