Jump to content

Varnish (software): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
Fenhl (talk | contribs)
53 edits
m →‎History: punctuation
Added secondary source
 
(40 intermediate revisions by 37 users not shown)
Line 1: Line 1:
{{Short description|HTTP accelerator software}}
{{self-published|date=June 2014}}
{{self-published|date=June 2014}}
{{Infobox software
{{Infobox software
Line 6: Line 7:
| caption =
| caption =
| developer = [[Poul-Henning Kamp]], [[Redpill-Linpro]], Varnish Software
| developer = [[Poul-Henning Kamp]], [[Redpill-Linpro]], Varnish Software
| latest release version = 6.1.1
| latest release version = {{wikidata|property|edit|reference|P548=Q2804309|P348}}
| latest release date = {{start date and age|{{wikidata|qualifier|P548=Q2804309|P348|P577}}}}
| latest release date = {{release date and age|2018|10|26}}<ref>{{cite web|url=http://varnish-cache.org/lists/pipermail/varnish-announce/2018-October/000730.html|accessdate=30 October 2018|date=26 October 2018|title=Varnish Cache 6.1.1 released|first=Pål Hermunn|last=Johansen|mailing-list=varnish-announce}}</ref>
| programming language = [[C (programming language)|C]]
| programming language = [[C (programming language)|C]]
| operating system = [[BSD]], [[Linux]], [[Unix]]
| operating system = [[BSD]], [[Linux]], [[Unix]]
Line 14: Line 15:
}}
}}


'''Varnish''' is an [[HTTP accelerator]] designed for content-heavy [[dynamic web site]]s as well as APIs. In contrast to other [[web accelerator]]s, such as [[Squid (software)|Squid]], which began life as a client-side cache, or [[Apache HTTP server|Apache]] and [[nginx]], which are primarily origin servers, Varnish was designed as an HTTP accelerator. Varnish is focused exclusively on [[HTTP]], unlike other [[proxy server]]s that often support [[FTP]], [[SMTP]] and other [[network protocol]]s.
'''Varnish''' is a [[Reverse proxy|reverse caching proxy]]<ref name="oreilly">{{Cite web |last=Feryn |first=Thijs |title=1. What Is Varnish Cache? - Getting Started with Varnish Cache [Book] |url=https://www.oreilly.com/library/view/getting-started-with/9781491972212/ch01.html |access-date=2023-10-22 |website=[[O'Reilly Media]]}}</ref> used as [[HTTP accelerator]] for content-heavy [[dynamic web site]]s as well as [[API]]s. In contrast to other [[web accelerator]]s, such as [[Squid (software)|Squid]], which began life as a client-side cache, or [[Apache HTTP server|Apache]] and [[nginx]], which are primarily [[Upstream server|origin servers]], Varnish was designed as an HTTP accelerator. Varnish is focused exclusively on [[HTTP]], unlike other [[proxy server]]s that often support [[FTP]], [[SMTP]], and other [[network protocol]]s.

Varnish is used by websites including [[Wikipedia]], online newspaper sites such as [[The New York Times]], [[The Guardian]], [[The Hindu]], ''[[Corriere della Sera]]'', social media and content sites such as [[Facebook]], [[Twitter]], [[Reddit]], [[Vimeo]], and [[Tumblr]]. In 2012, 5% of the top 10,000 sites in the web used the software.<ref>{{cite web|url=http://royal.pingdom.com/2012/07/11/how-popular-is-varnish/|title=How popular is Varnish}}</ref>


==History==
==History==
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]] core 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.
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]]<ref name="oreilly" /> (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 is [[free and open source software]], available under a two-clause [[BSD license]]. Commercial support is available from Varnish Software, amongst others.
Varnish is [[free and open source software]], available under a two-clause [[BSD license]]. Commercial support is available from Varnish Software, amongst others.


Version 1.0 of Varnish was released in 2006,<ref>[http://www.catalystframework.org/calendar/2008/14 "Making Catalyst Sites Shine with Varnish", Dec. 14, 2008]</ref><ref>[https://www.varnish-cache.org/lists/pipermail/varnish-announce/2006-September/000638.html "Varnish 1.0 released", Sep. 20, 2006]</ref> Varnish 2.0 in 2008,<ref>[https://www.varnish-cache.org/lists/pipermail/varnish-announce/2008-October/000010.html "Varnish 2.0 released", Oct. 15 2008]</ref> Varnish 3.0 in 2011,<ref>[https://www.varnish-cache.org/lists/pipermail/varnish-announce/2011-June/000670.html "Varnish 3.0.0 released", Jun. 16 2011]</ref> Varnish 4.0 in 2014,<ref>[https://www.varnish-cache.org/lists/pipermail/varnish-announce/2014-April/000696.html "Varnish 4.0.0 released", Apr. 10 2014]</ref> Varnish 5.0 in 2016,<ref>[http://www.varnish-cache.org/releases/rel5.0.0.html "Varnish Cache 5.0", Sep. 15, 2016]</ref> and Varnish 6.0 in March 2018.<ref>{{cite web|url=https://varnish-cache.org/lists/pipermail/varnish-announce/2018-March/000726.html|accessdate=15 May 2018|date=15 March 2018|title=Varnish 6.0 Released|author=Poul-Henning Kamp}}</ref>
Version 1.0 of Varnish was released in 2006,<ref>{{Cite web|url=http://www.catalystframework.org/calendar/2008/14|title=Catalyst Advent Calendar - Day 14|website=www.catalystframework.org|access-date=Sep 4, 2020}}</ref><ref>{{Cite web|url=https://varnish-cache.org/lists/pipermail/varnish-announce/2006-September/000638.html|title=Varnish 1.0 released|first=Dag-Erling|last=Smørgrav|date=Sep 20, 2006|access-date=Sep 4, 2020}}</ref> Varnish 2.0 in 2008,<ref>{{Cite web|url=https://varnish-cache.org/lists/pipermail/varnish-announce/2008-October/000010.html|title=Varnish 2.0 released!|first=Tollef Fog|last=Heen|date=Oct 15, 2008|access-date=Sep 4, 2020}}</ref> Varnish 3.0 in 2011,<ref>{{Cite web|url=https://varnish-cache.org/lists/pipermail/varnish-announce/2011-June/000670.html|title=Varnish 3.0.0 released|first=Tollef Fog|last=Heen|date=Jun 17, 2011|access-date=Sep 4, 2020}}</ref> Varnish 4.0 in 2014,<ref>{{Cite web|url=https://varnish-cache.org/lists/pipermail/varnish-announce/2014-April/000696.html|title=Varnish 4.0.0 released|first=Lasse|last=Karstensen|date=Apr 10, 2014|access-date=Sep 4, 2020}}</ref> Varnish 5.0 in 2016,<ref>{{Cite web|url=http://varnish-cache.org/releases/rel5.0.0.html|title=Varnish Cache 5.0.0 — Varnish HTTP Cache|website=varnish-cache.org|access-date=Sep 4, 2020}}</ref> Varnish 6.0 in March 2018,<ref>{{cite web|url=https://varnish-cache.org/lists/pipermail/varnish-announce/2018-March/000726.html|access-date=15 May 2018|date=15 March 2018|title=Varnish 6.0 Released|author=Poul-Henning Kamp}}</ref> and Varnish 7.0 in September 2021.<ref>{{cite web|url=https://varnish-cache.org/lists/pipermail/varnish-announce/2021-September/000747.html|access-date=9 August 2022|date=9 August 2022|title=Varnish Cache 7.0.0 released|author=Poul-Henning Kamp}}</ref>


==Architecture==
==Architecture==
Line 30: Line 29:
Varnish is heavily [[Thread (computer science)|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.
Varnish is heavily [[Thread (computer science)|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.{{cn|date=May 2018}} When a VCL script is loaded, it is translated to [[C (programming language)|C]], compiled to a shared object by the system compiler, and loaded directly into the accelerator which can thus be reconfigured without a restart.
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.{{citation needed|date=May 2018}} When a VCL script is loaded, it is translated to [[C (programming language)|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.
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 (interprocess communication)|shared memory]], and the task of monitoring, filtering, formatting and writing log data to disk is delegated to a separate application.
In order to reduce the number of system calls in the fast path to a minimum, log data is stored in [[shared memory (interprocess communication)|shared memory]], and the task of monitoring, filtering, formatting and writing log data to disk is delegated to a separate application.

==Performance==
While Varnish is designed to reduce contention between threads to a minimum, its authors claim{{Citation needed|date=August 2012}} that its performance will only be as good as that of the system's [[POSIX Threads|pthreads]] implementation.

Additionally, a slow [[malloc]] implementation (like the ones in [[Microsoft Windows]]'s msvcrt<ref>{{cite web|url=http://www.perlmonks.org/bare/?node_id=810307 |title=Re: Why is Windows 100 times slower than Linux when growing a large scalar?}}</ref><ref>http://locklessinc.com/benchmarks_allocator.shtml</ref>) may add unnecessary contention and thereby limit performance, hence the general recommendation of running Varnish on Linux or Unix based environments.


===Performance metrics===
===Performance metrics===
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:<ref>{{cite web|url=https://www.datadoghq.com/blog/top-varnish-performance-metrics/|title=Top Varnish performance metrics}}</ref>
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:<ref>{{Cite web|url=https://www.datadoghq.com/blog/top-varnish-performance-metrics/|title=Top Varnish performance metrics|date=Jul 28, 2015|website=Top Varnish performance metrics|access-date=Sep 4, 2020}}</ref>
* '''Client metrics''': client connections and requests
* '''Client metrics''': client connections and requests
* '''[[Cache (computing)|Cache]] performance''': cache hits, evictions
* '''Cache performance''': [[Cache (computing)|cache]] hits, evictions
* '''Thread metrics''': thread creation, failures, queues
* '''Thread metrics''': thread creation, failures, queues
* '''[[Front and back ends|Backend]] metrics''': success, failure, and health of backend connections
* '''Backend metrics''': success, failure, and health of [[Front and back ends|backend]] connections


===Metric collection===
===Metric collection===
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.<ref>{{cite web|url=https://www.datadoghq.com/blog/how-to-collect-varnish-metrics/|title=How to collect Varnish metrics}}</ref>
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.<ref>{{Cite web|url=https://www.datadoghq.com/blog/how-to-collect-varnish-metrics/|title=How to collect Varnish metrics|date=Jul 28, 2015|website=How to collect Varnish metrics|access-date=Sep 4, 2020}}</ref>

====varnishstat====
====varnishstat====
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.<ref>{{cite web|url=https://linux.die.net/man/1/varnishstat|title=varnishstat - Linux man page}}</ref>
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.<ref>{{Cite web|url=https://linux.die.net/man/1/varnishstat|title=varnishstat(1): HTTP accelerator statistics - Linux man page|website=linux.die.net|access-date=Sep 4, 2020}}</ref> 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.

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.
[[File:Varnishlog Example.png|thumb|Varnishlog running with a Wikimedia backend]]

==== varnishlog====
==== varnishlog====
varnishlog is a tool that can be used to debug or tune Varnish's configuration, as it provides detailed information about each individual request.
Varnishlog is a tool that can be used to debug or tune Varnish's configuration, as it provides detailed information about each individual request.


==Load balancing==
==Load balancing==
Varnish supports [[Load balancing (computing)|load balancing]] using both a [[round-robin scheduling|round robin]] and a random director, both with a per-backend weighting. Basic health-checking of backends is also available.<ref>{{cite web|url=https://www.varnish-cache.org/wiki/BackendPolling |title=BackendPolling – Varnish |publisher=Varnish-cache.org |date= |accessdate=2014-07-18}}</ref>
Varnish supports [[Load balancing (computing)|load balancing]] using both a [[round-robin scheduling|round robin]] and a random director, both with a per-backend weighting. Basic health-checking of backends is also available.<ref>{{cite web |url=https://www.varnish-cache.org/wiki/BackendPolling |title=BackendPolling – Varnish |publisher=Varnish-cache.org |access-date=2014-07-18 |archive-date=2010-08-21 |archive-url=https://web.archive.org/web/20100821130306/http://www.varnish-cache.org/wiki/BackendPolling |url-status=dead }}</ref>


==Other features==
==Other features==
Varnish Cache also features:
Varnish Cache also features:
* Plugin support with Varnish Modules, also called [[VMODs]]<ref>{{cite web|url=https://www.varnish-cache.org/vmods |title=VMODs Directory (Varnish Modules and Extensions) &#124; Varnish Community |publisher=Varnish-cache.org |date= |accessdate=2014-07-18}}</ref>
* Plugin support with Varnish Modules, also called [[VMODs]]<ref>{{cite web|url=https://www.varnish-cache.org/vmods |title=VMODs Directory (Varnish Modules and Extensions) &#124; Varnish Community |publisher=Varnish-cache.org |access-date=2014-07-18}}</ref>
* Support for [[Edge Side Includes]] including stitching together compressed ESI fragments
* Support for [[Edge Side Includes]] including stitching together compressed ESI fragments
* [[Gzip]] Compression and Decompression
* [[Gzip]] Compression and Decompression
Line 71: Line 68:
|website=Varnish
|website=Varnish
|url=https://www.varnish-cache.org/trac/wiki/VCLExampleSaintMode
|url=https://www.varnish-cache.org/trac/wiki/VCLExampleSaintMode
|archive-url=https://web.archive.org/web/20110507034955/https://www.varnish-cache.org/trac/wiki/VCLExampleSaintMode
|archive-date=7 May 2011
}}</ref> and Grace<ref name="Varnish, Grace" >{{Cite web
}}</ref> and Grace<ref name="Varnish, Grace" >{{Cite web
|title=Grace Mode
|title=Grace Mode
|website=Varnish
|website=Varnish
|url=https://www.varnish-cache.org/trac/wiki/VCLExampleGrace
|url=https://www.varnish-cache.org/trac/wiki/VCLExampleGrace
|archive-url=https://web.archive.org/web/20110509101258/https://www.varnish-cache.org/trac/wiki/VCLExampleGrace
|archive-date=9 May 2011
}}</ref><ref name="Getting Started">{{Cite book
|title=Getting Started with Varnish Cache: Accelerate Your Web Applications
|last=Feryn
|first=Thijs
|year=2017
|page=85
|publisher=O'Reilly Media, Inc
|isbn=9781491972229
}}</ref> modes.
}}</ref> modes.
: If a server malfunctions and returns 500 errors, Grace mode will ignore expiry headers and continue to return cached versions. Saint mode is for use when [[load balancing (computing)|load balancing]], where a failing server is blacklisted for a quarantine period and excluded from the server pool.
** If a server malfunctions and returns [[List of HTTP status codes#5xx server errors|HTTP status code 500]], Grace mode will ignore expiry headers and continue to return cached versions. Saint mode is for use when [[load balancing (computing)|load balancing]], where a failing server is blocked for a quarantine period and excluded from the server pool.


==See also==
==See also==
{{Portal|Free software}}
{{Portal|Free and open-source software}}
* [[Web accelerator]] which discusses host-based HTTP acceleration
* [[Web accelerator]] which discusses host-based HTTP acceleration
* [[Proxy server]] which discusses client-side proxies
* [[Proxy server]] which discusses client-side proxies
Line 85: Line 94:
* [[Comparison of web servers]]
* [[Comparison of web servers]]
* [[Internet Cache Protocol]]
* [[Internet Cache Protocol]]
* [[Guru Meditation]] – an error message used by Varnish


==References==
==References==
Line 105: Line 115:
[[Category:Cross-platform software]]
[[Category:Cross-platform software]]
[[Category:Forward proxy]]
[[Category:Forward proxy]]
[[Category:Software using the BSD license]]

Latest revision as of 11:23, 22 October 2023

Varnish
Developer(s)Poul-Henning Kamp, Redpill-Linpro, Varnish Software
Stable release
7.4.2[1] Edit this on Wikidata / 13 November 2023; 7 months ago (13 November 2023)
Repository
Written inC
Operating systemBSD, Linux, Unix
TypeHTTP accelerator
Licensetwo-clause BSD license
Websitevarnish-cache.org Edit this on Wikidata

Varnish is a reverse caching proxy[2] used as HTTP accelerator 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.

History[edit]

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[2] (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 is free and open source software, available under a two-clause BSD license. Commercial support is available from Varnish Software, amongst others.

Version 1.0 of Varnish was released in 2006,[3][4] Varnish 2.0 in 2008,[5] Varnish 3.0 in 2011,[6] Varnish 4.0 in 2014,[7] Varnish 5.0 in 2016,[8] Varnish 6.0 in March 2018,[9] and Varnish 7.0 in September 2021.[10]

Architecture[edit]

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.[citation needed] 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.

Performance metrics[edit]

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:[11]

  • 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

Metric collection[edit]

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.[12]

varnishstat[edit]

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.[13] 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 running with a Wikimedia backend

varnishlog[edit]

Varnishlog is a tool that can be used to debug or tune Varnish's configuration, as it provides detailed information about each individual request.

Load balancing[edit]

Varnish supports load balancing using both a round robin and a random director, both with a per-backend weighting. Basic health-checking of backends is also available.[14]

Other features[edit]

Varnish Cache also features:

  • Plugin support with Varnish Modules, also called VMODs[15]
  • 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[16] and Grace[17][18] modes.
    • If a server malfunctions and returns HTTP status code 500, Grace mode will ignore expiry headers and continue to return cached versions. Saint mode is for use when load balancing, where a failing server is blocked for a quarantine period and excluded from the server pool.

See also[edit]

References[edit]

  1. ^ "Releases & Downloads". Retrieved 4 December 2023.
  2. ^ a b Feryn, Thijs. "1. What Is Varnish Cache? - Getting Started with Varnish Cache [Book]". O'Reilly Media. Retrieved 2023-10-22.
  3. ^ "Catalyst Advent Calendar - Day 14". www.catalystframework.org. Retrieved Sep 4, 2020.
  4. ^ Smørgrav, Dag-Erling (Sep 20, 2006). "Varnish 1.0 released". Retrieved Sep 4, 2020.
  5. ^ Heen, Tollef Fog (Oct 15, 2008). "Varnish 2.0 released!". Retrieved Sep 4, 2020.
  6. ^ Heen, Tollef Fog (Jun 17, 2011). "Varnish 3.0.0 released". Retrieved Sep 4, 2020.
  7. ^ Karstensen, Lasse (Apr 10, 2014). "Varnish 4.0.0 released". Retrieved Sep 4, 2020.
  8. ^ "Varnish Cache 5.0.0 — Varnish HTTP Cache". varnish-cache.org. Retrieved Sep 4, 2020.
  9. ^ Poul-Henning Kamp (15 March 2018). "Varnish 6.0 Released". Retrieved 15 May 2018.
  10. ^ Poul-Henning Kamp (9 August 2022). "Varnish Cache 7.0.0 released". Retrieved 9 August 2022.
  11. ^ "Top Varnish performance metrics". Top Varnish performance metrics. Jul 28, 2015. Retrieved Sep 4, 2020.
  12. ^ "How to collect Varnish metrics". How to collect Varnish metrics. Jul 28, 2015. Retrieved Sep 4, 2020.
  13. ^ "varnishstat(1): HTTP accelerator statistics - Linux man page". linux.die.net. Retrieved Sep 4, 2020.
  14. ^ "BackendPolling – Varnish". Varnish-cache.org. Archived from the original on 2010-08-21. Retrieved 2014-07-18.
  15. ^ "VMODs Directory (Varnish Modules and Extensions) | Varnish Community". Varnish-cache.org. Retrieved 2014-07-18.
  16. ^ "Saint Mode". Varnish. Archived from the original on 7 May 2011.
  17. ^ "Grace Mode". Varnish. Archived from the original on 9 May 2011.
  18. ^ Feryn, Thijs (2017). Getting Started with Varnish Cache: Accelerate Your Web Applications. O'Reilly Media, Inc. p. 85. ISBN 9781491972229.

External links[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Varnish_(software)&oldid=1181332190"