Vinyl Cache

From Wikipedia, the free encyclopedia

Template:Short description

Page Module:Message box/ambox.css has no content.

Page Module:Infobox/styles.css has no content.

Vinyl Cache
Other namesVarnish Cache
[[Programmer|DeveloperTemplate:Pluralize from text]]Poul-Henning Kamp, Redpill-Linpro, Varnish Software
Template:Infobox software/simple
Written inC
EnginePage Template:Plainlist/styles.css has no content.
Template:EditAtWikidata
Operating systemBSD, Linux, Unix
TypeHTTP accelerator
Licensetwo-clause BSD license
WebsiteScript error: No such module "WikidataIB".
RepositoryPage Template:Plainlist/styles.css has no content.

Script error: No such module "Check for conflicting parameters".

Vinyl Cache, formerly Varnish Cache[1], 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, Vinyl Cache was designed as an HTTP accelerator. Vinyl Cache is focused exclusively on HTTP, unlike other proxy servers that often support FTP, SMTP, and other network protocols.

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[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

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.[11] 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 principle 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][<span title="Script error: No such module "decodeEncode".">example 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

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

  • 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

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

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

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

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

Other features

Varnish Cache also features:

  • Plugin support with Varnish Modules, also called VMODs[16]
  • 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[17] and Grace[18][19] 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

Lua error in mw.title.lua at line 404: bad argument #2 to 'title.new' (unrecognized namespace name 'Portal').

References

Page Template:Reflist/styles.css has no content.

  1. ^ Page Module:Citation/CS1/styles.css has no content."On Vinyl Cache and Varnish Cache - Vinyl Cache". vinyl-cache.org. Retrieved 2026-05-31.
  2. ^ a b Page Module:Citation/CS1/styles.css has no content.Feryn, Thijs (2017). 1. What Is Varnish Cache? - Getting Started with Varnish Cache [Book]. O'Reilly Media, Incorporated. ISBN 978-1-4919-7221-2. Retrieved 2023-10-22.
  3. ^ Page Module:Citation/CS1/styles.css has no content."Catalyst Advent Calendar - Day 14". www.catalystframework.org. Archived from the original on July 9, 2012. Retrieved Sep 4, 2020.
  4. ^ Page Module:Citation/CS1/styles.css has no content.Smørgrav, Dag-Erling (Sep 20, 2006). "Varnish 1.0 released". Retrieved Sep 4, 2020.
  5. ^ Page Module:Citation/CS1/styles.css has no content.Heen, Tollef Fog (Oct 15, 2008). "Varnish 2.0 released!". Retrieved Sep 4, 2020.
  6. ^ Page Module:Citation/CS1/styles.css has no content.Heen, Tollef Fog (Jun 17, 2011). "Varnish 3.0.0 released". Retrieved Sep 4, 2020.
  7. ^ Page Module:Citation/CS1/styles.css has no content.Karstensen, Lasse (Apr 10, 2014). "Varnish 4.0.0 released". Retrieved Sep 4, 2020.
  8. ^ Page Module:Citation/CS1/styles.css has no content."Varnish Cache 5.0.0 — Varnish HTTP Cache". varnish-cache.org. Retrieved Sep 4, 2020.
  9. ^ Page Module:Citation/CS1/styles.css has no content.Poul-Henning Kamp (15 March 2018). "Varnish 6.0 Released". Retrieved 15 May 2018.
  10. ^ Page Module:Citation/CS1/styles.css has no content.Poul-Henning Kamp (9 August 2022). "Varnish Cache 7.0.0 released". Retrieved 9 August 2022.
  11. ^ Page Module:Citation/CS1/styles.css has no content."Distributing digital media: How we improved throughput by 4x". BBC Blogs. 17 Dec 2015. Retrieved 17 September 2025.
  12. ^ Page Module:Citation/CS1/styles.css has no content."Top Varnish performance metrics". Top Varnish performance metrics. Jul 28, 2015. Retrieved Sep 4, 2020.
  13. ^ Page Module:Citation/CS1/styles.css has no content."How to collect Varnish metrics". How to collect Varnish metrics. Jul 28, 2015. Retrieved Sep 4, 2020.
  14. ^ Page Module:Citation/CS1/styles.css has no content."varnishstat(1): HTTP accelerator statistics - Linux man page". linux.die.net. Retrieved Sep 4, 2020.
  15. ^ Page Module:Citation/CS1/styles.css has no content."BackendPolling – Varnish". Varnish-cache.org. Archived from the original on 2010-08-21. Retrieved 2014-07-18.
  16. ^ Page Module:Citation/CS1/styles.css has no content."VMODs Directory (Varnish Modules and Extensions) | Varnish Community". Varnish-cache.org. Retrieved 2014-07-18.
  17. ^ Page Module:Citation/CS1/styles.css has no content."Saint Mode". Varnish. Archived from the original on 7 May 2011.
  18. ^ Page Module:Citation/CS1/styles.css has no content."Grace Mode". Varnish. Archived from the original on 9 May 2011.
  19. ^ Page Module:Citation/CS1/styles.css has no content.Feryn, Thijs (2017). Getting Started with Varnish Cache: Accelerate Your Web Applications. O'Reilly Media, Inc. p. 85. ISBN 9781491972229.

Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found.

Retrieved from "http://cosmopedia.co/index.php?title=Vinyl_Cache&oldid=3276973"