Plone secrets: Episode 4 - Varnish in front#

This just in from the production department: use Varnish. (And please forgive the heavily meme-laden approach to describing these techniques.)

Cache ALL the hosts#

Our ability to use Varnish in production is no secret by now, or at least it shouldn’t be. What is often less clear is exactly how to use it. One way I like[1], is to run Varnish on your public IP port 80 and make Apache listen on your private IP port 80. Then proxy from Varnish to Apache and enjoy easy caching goodness on all your virtual hosts in Apache.


This should require less than five minutes of down time to implement. First, configure the appropriate settings. (Well, first install Apache and Varnish if you haven’t already: `aptitude install varnish apache2` on Ubuntu Linux[0].)


To modify the listen IP address and port, we typically edit a file like /etc/default/varnish (in Ubuntu). However you do it, configure the equivalent of the following on your system:

             -T localhost:6082
             -f /etc/varnish/default.vcl
             -s malloc,256m"

This environment variable is then passed to varnishd on the command line. Next, pass traffic to Apache like so (in /etc/varnish/default.vcl on Ubuntu):

backend default {
 .host = "";
 .port = "80";

Now on to Apache.

*Please note that the syntax above is for Varnish 3.x and the syntax has (annoyingly) changed from 2.x to 3.x.*


The Apache part is a bit simpler. You just need to change the listen port (on Ubuntu this is done in /etc/apache2/ports.conf), typically from something like:

Listen *:80



Restart ALL the services#

Now restart both services. If all goes well you shouldn’t notice any difference, except better performance, and when you make a website change and need to clear the cache[2]. For this, I rely on telnetting to the varnish port and issuing the `ban.url` command (formerly `url.purge` in 2.x):

$ telnet localhost 6082
Connected to localhost.
Escape character is '^]'.
200 205
Varnish Cache CLI 1.0
Linux,,x86_64,-smalloc,-smalloc,-hcritbitType 'help' for command list.
Type 'quit' to close CLI session.ban.url /
200 0

Cache ALL the disks#

This site has Varnish and Apache configured as described in this article. It also has disk caching in Apache enabled, thanks to Elizabeth Leddy’s article:

As a result, it’s PEPPY AS THE DICKENS™ on a 512MB “slice” (Cloud server) from Rackspace Cloud. And now you know yet another “Plone secret”. Now go make your Plone sites faster, and let me know how it goes in the comments section below.


[0] Using the latest distribution, “oneric”.

[1] I first saw this technique at NASA when NASA Science was powered by Plone; I found it odd at the time but years later it makes perfect sense.

[2] Ideally you’d configure this in p.a.caching, but I’ve not been able to stomach this yet.