Pak Jiddat - Innovative Software Services

Read: In the name of thy Lord Who createth, Createth man from a clot. Read: And thy Lord is the Most Bounteous, Who teacheth by the pen, Teacheth man that which he knew not. Nay, but verily man is rebellious That he thinketh himself independent!. Lo! unto thy Lord is the return. (Sura Alalaq 96:8)

Tuning WordPress performance using Varnish

Created On: 11 Apr, 2017: 12:30:09 - Tags : content management systems | website testing


Recently I had the opportunity of working on tuning website performance using Varnish. Varnish is called a Caching HTTP Reverse Proxy. This means it sits between your end user and one or more backend servers such as apache or nginx and functions as a cache for HTTP traffic. Varnish can also function as a backend server for a frontend such as Haproxy. This is the configuration in which we used Varnish. Using Varnish is an excellent option for busy websites. It is a very fast and efficient caching server that can greatly reduce the time taken for serving requests. Of course to get maximum benefit from Varnish we need to configure and tune it according to our needs. I will describe my experience of configuring and tuning Varnish in this blog post.

Installing Varnish

Varnish online documentation is complete and covers all aspects of using Varnish from installation to configuration and troubleshooting. Installation for Redhat based systems is simple and only requires adding the varnish repository to yum and running yum install varnish. This will install the latest version of varnish on your server. The latest version of varnish is 4.0.x. The 4.x branch of Varnish is very different from the 3.x branch so Varnish configuration for 3.x will probably not work on 4.x. Its also difficult to find code samples for 4.x branch. If you need help with tuning Varnish you should read their documentation and their online support forum. Changes from the 3.x branch are documented on the Varnish website.

Basic Configuration

Once we installed Varnish on our Centos 6 server we configured it to listen on port 80 and configured Apache to listen on port 8008. To change listen port of Varnish we set the VARNISH_LISTEN_PORT=80 in the main Varnish configuration file /etc/sysconfig/varnish. To change Apache port to 8008 we had to edit /etc/httpd/conf/httpd.conf and add port 8008 to the Listen directive. Port 8008 also needs to be added to all the VirtualHost directives that will serve content to Varnish. After making the changes to Apache configuration file we restarted Apache using service httpd restart. After that we changed the Varnish backend port to 8008. This tells Varnish to communicate with Apache over port 8008. To do this we set .port = "8008" in /etc/varnish/default.vcl and restarted Varnish using service varnish restart. Varnish can store its content in memory or in files. To configure Varnish so it saves content in memory we had to set VARNISH_STORAGE="malloc,${VARNISH_STORAGE_SIZE}" in /etc/sysconfig/varnish. Thats all that is needed for getting up and running with Varnish.

Serving content over Varnish

We had to tune and configure Varnish so it allows delivering content from our custom Content Delivery Network. We also had to configure Varnish so it supports WordPress. To do this we had to edit the main Varnish configuration file: /etc/sysconfig/varnish and the default varnish configuration file /etc/varnish/default.vcl.

Adding Content Delivery Network (CDN) server to Varnish

To add our Content Delivery Network (CDN) server to Varnish we did following:
  1. Edited /etc/varnish/default.vcl and added following lines below the backend statement: backend cdn { .host = ""; .port = "8000"; }. is the ip address of the CDN server. 8000 is http listen port of the CDN server.
  2. We then restarted Varnish
  3. We also had to update the DNS record for the CDN host name so it points to our Varnish server. Once we did that our CDN content was being served over Varnish.

Serving WordPress over Varnish

In order to serve our WordPress website over Varnish we had to add specific configuration information for WordPress to /etc/varnish/default.vcl. This file contains configuration information in a language called "Varnish Control Language" or VCL. Using this language we can configure Varnish for various tasks. The VCL configuration file contains sub routines that correspond to different stages of request execution in Varnish. These sub routines are documented in the default.vcl files. They are:
  1. vcl_recv. This is called by varnish just before it checks if the request is in cache or not. In this sub routine we can clear cookies from the request or rewrite the request.
  2. vcl_backend_response. This is called just before Varnish reads the HTTP response headers from the backend. In this sub routine we can clear cookies that are set by the backend.
  3. vcl_deliver. This is called just before the response is sent to the client. In this sub routine we can do basic accounting tasks or modify the final object before it is delivered to the client. For example we can set a HTTP response header indicating if the request was a cache hit or a cache miss. The following VCL code can achieve this:

Adding HTTP headers to Varnish output

If you have multiple Varnish backends. For example you have one HAProxy frontend that load balances between multiple Varnish backends, then it would be useful to know which Varnish backend served a request. You can do this be using the following vcl code in vcl_deliver sub routine.
sub vcl_deliver {
resp.http.X-Server= "";
It sets the server name to You can view the http headers added by Varnish such as cache hit/miss, cache duration etc from Google Chrome's Developer Toolbox.

Download the VCL

Varnish has some useful VCL code for WordPress but it only works with Varnish 3.x. I had to modify the code so it works with Varnish 4.x.

Varnish plugin for WordPress

WordPress has a useful plugin for Varnish called Varnish HTTP Purge. It allows WordPress admin users to remove or purge pages from the Varnish cache. We were using WTC Total Cache plugin which has basic support for Varnish. It allows us to purge the Varnish cache. This was enough for our needs so we did not need to install another plugin.

Securing Varnish

One of the tasks that are commonly carried out in Varnish is purging content from the Varnish cache. By default Varnish allows purging content from any host. This can create a security issue, so its best to configure Varnish so it allows purging content from local host or specific ips. To do this we need to create an Access Control List in Varnish that defines which hosts are allowed to purge Varnish cache. The following VCL statements achieved this: Place following after the backend statements:
acl purge {
Place following inside vcl_recv sub routine. It checks the HTTP request method. If the method is PURGE and the ip from where the purge request is made is supported by the above acl then the object is purged from the Varnish cache and the next vcl statement is executed. If the ip is not supported by the acl then an error is shown to the user:
if (req.method == "PURGE") {
if (!client.ip } purge) {
return(synth(405,"Not allowed."));
return (purge);
Place following inside vcl_hit sub routine. vcl_hit is the function that is called when the object is found in the Varnish cache. If the request method is PURGE then Varnish returns success.
if (req.method == "PURGE") {    
Place following inside vcl_miss sub routine. vcl_miss is the function that is called when the object is not found in the Varnish cache. If the request method is PURGE and the object was not found in the cache, then the sub routine returns success since the object was not in cache anyway.
if (req.method == "PURGE") {    

You can also purge content from the Varnish cache using following command line: curl -X PURGE content_url. Make sure you issue this command from a host that is allowed by the acl that you defined in your varnish vcl file.

The VCL configuration file of WordPress performs 2 main tasks. One is to allow purging of Varnish content from certain ips. The other is to remove cookies from client http requests and backend http response. Varnish never caches content that has cookies. So any content that needs to be cached must be stripped of all cookies.

Of course you don't want to cache content from WordPress admin pages so you need to add suitable vcl statements that exclude the admin pages from being cached. Another thing to note about Varnish is that it considers objects with different url query strings as different. So if you want to remove a JavaScript file from being cached one option is to append a query string to the url and change the query string each time the JavaScript file is updated and needs to be removed from the Varnish cache.

Checking errors

If you have an error in your vcl configuration file and you restart Varnish, then at least on Centos servers you wont see any descriptive error message. To see the error message you can start varnish manually from the command line using following: vanrishd -f /etc/varnish/default.vcl. This will show the errors in the vcl configuration.

Viewing statistics

Varnish also has built in tools for viewing statistics. These tools are:
  • varnishtop. it reads the varnish shared memory logs and presents a list of the most commonly updated log entries. e.g it can list ranking of requested documents, clients, user agents etc.
  • varnishhist. it reads shared memory logs and displays continuously updated histogram showing distribution of last N requests.
  • varnishtop. it displays different varnish counters such as hit rate, miss rate, information about storage, threads created, deleted objects etc.

Edge side includes

Varnish also has a feature called edge side includes or ESI. This allows different caching policies to be applied to different parts of a web page. For example if a web page includes a statement such as , then that will cause Varnish to replace the include statement with the content. This can be used for example by a news web site for caching the list of top 10 news items. Varnish is a very popular choice for use as HTTP cache. Many I.T tools provide support for Varnish. For example the monitoring tool, Munin has a plugin for Varnish that allows users to graph Varnish statistics.


While there are other HTTP caches such as Squid, I found Varnish to be an excellent option. It has many configuration options, its easy to configure, it has good statistics and log monitoring tools and is actively developed.

Related Articles

  1. Creating custom themes for October CMS
  2. Developing WordPress plugins using Pak Php framework - Part 2
  3. Developing WordPress plugins using Pak Php framework - Part 1
  4. Validate your WordPress blog using WordPress XML-RPC API, Php Tidy and Nu HTML Checker
  5. WordPress Deployment with Jenkins and Redmine
  6. Improving WordPress Performance
  7. Creating your own WordPress themes and plugins
  8. WordPress for small and medium businesses
  9. Some excellant Wordpress Plugins