This article may contain excessive or inappropriate references to self-published sources. (June 2014) (Learn how and when to remove this template message)
|Developer(s)||Poul-Henning Kamp, Redpill-Linpro, Varnish Software|
6.4.0 / March 16, 2020
|Operating system||BSD, Linux, Unix|
|License||two-clause BSD license|
Varnish is an HTTP accelerator designed for content-heavy dynamic web sites as well as APIs. In contrast to other web accelerators, such as Squid, which began life as a client-side cache, or Apache and nginx, which are primarily origin servers, Varnish was designed as an HTTP accelerator. Varnish is focused exclusively on HTTP, unlike other proxy servers that often support FTP, SMTP and other network protocols.
The project was initiated by the online branch of the Norwegian tabloid newspaper Verdens Gang. The architect and lead developer is Danish independent consultant Poul-Henning Kamp (a well-known FreeBSD developer), with management, infrastructure and additional development originally provided by the Norwegian Linux consulting company Linpro. The support, management and development of Varnish was later spun off into a separate company, Varnish Software.
Varnish stores data in virtual memory and leaves the task of deciding what is stored in memory and what gets paged out to disk to the operating system. This helps avoid the situation where the operating system starts caching data while it is moved to disk by the application.
Varnish is heavily threaded, with each client connection being handled by a separate worker thread. When the configured limit on the number of active worker threads is reached, incoming connections are placed in an overflow queue; when this queue reaches its configured limit incoming connections will be rejected.
The principal configuration mechanism is Varnish Configuration Language (VCL), a domain-specific language (DSL) used to write hooks that are called at critical points in the handling of each request. Most policy decisions are left to VCL code, making Varnish more configurable and adaptable than most other HTTP accelerators. When a VCL script is loaded, it is translated to C, compiled to a shared object by the system compiler, and loaded directly into the accelerator which can thus be reconfigured without a restart.
A number of run-time parameters control things such as the maximum and the minimum number of worker threads, various timeouts, etc. A command-line management interface allows these parameters to be modified, and new VCL scripts to be compiled, loaded and activated, without restarting the accelerator.
In order to reduce the number of system calls in the fast path to a minimum, log data is stored in shared memory, and the task of monitoring, filtering, formatting and writing log data to disk is delegated to a separate application.
While Varnish is designed to reduce contention between threads to a minimum, its authors claim that its performance will only be as good as that of the system's pthreads implementation.
Additionally, a slow malloc implementation (like the ones in Microsoft Windows's msvcrt) may add unnecessary contention and thereby limit performance, hence the general recommendation of running Varnish on Linux or Unix based environments.
Varnish Cache can speed up information delivery by a factor of several hundred. To ensure proper operation and performance, Varnish exposes metrics that can be monitored in the following areas:
- Client metrics: client connections and requests
- Cache performance: cache hits, evictions
- Thread metrics: thread creation, failures, queues
- Backend metrics: success, failure, and health of backend connections
Varnish Cache ships with monitoring and logging tools. One of the most used is varnishstat which gives a detailed snapshot of Varnish’s current performance. It provides access to in-memory statistics such as cache hits and misses, resource consumption, threads created, and more.
Running varnishstat from the command line returns a continuously updating list of all available Varnish metrics. If the -1 flag is added, varnishstat will exit after printing the list one time. Varnishstat can be used as a standalone tool to spot-check the health of the cache. In order to graph metrics over time, correlate with other statistics from across an infrastructure, and set up alerts about any problems that may arise, monitoring services can integrate with Varnish and collect varnishstat metrics.
varnishlog is a tool that can be used to debug or tune Varnish's configuration, as it provides detailed information about each individual request.
Varnish Cache also features:
- Plugin support with Varnish Modules, also called VMODs
- Support for Edge Side Includes including stitching together compressed ESI fragments
- Gzip Compression and Decompression
- DNS, Random, Hashing and Client IP-based Directors
- HTTP Streaming Pass & Fetch
- Experimental support for Persistent Storage, without LRU eviction
- Saint and Grace modes.
- Web accelerator which discusses host-based HTTP acceleration
- Proxy server which discusses client-side proxies
- Reverse proxy which discusses origin-side proxies
- Comparison of web servers
- Internet Cache Protocol
- "Varnish Cache 6.4.0 is released". 16 March 2020.
- "Making Catalyst Sites Shine with Varnish", Dec. 14, 2008
- "Varnish 1.0 released", Sep. 20, 2006
- "Varnish 2.0 released", Oct. 15 2008
- "Varnish 3.0.0 released", Jun. 16 2011
- "Varnish 4.0.0 released", Apr. 10 2014
- "Varnish Cache 5.0", Sep. 15, 2016
- Poul-Henning Kamp (15 March 2018). "Varnish 6.0 Released". Retrieved 15 May 2018.
- "Re: Why is Windows 100 times slower than Linux when growing a large scalar?".
- "Top Varnish performance metrics".
- "How to collect Varnish metrics".
- "varnishstat - Linux man page".
- "BackendPolling – Varnish". Varnish-cache.org. Retrieved 2014-07-18.
- "VMODs Directory (Varnish Modules and Extensions) | Varnish Community". Varnish-cache.org. Retrieved 2014-07-18.
- "Saint Mode". Varnish.
- "Grace Mode". Varnish.