Search
Varnish Enterprise

Introduction Installation Upgrading Troubleshooting Changelog Changelog for 6.0.x Changes (Varnish Cache 4.1) Changes (Varnish Cache Plus 4.1) Known Issues Features Backend SSL/TLS Client SSL/TLS termination Cluster In-Process TLS MSE 4 Basic Configuration / Getting Started Configuration Persisted caching Categories Configuration Reference MSE 3.0 Settings mkfs.mse Memory Governor MSE 2.0 NUMA Parallel ESI Backend health counter HTTP/2 Support JSON Logging TCP Only Probes Timeouts Transit Buffer Varnish scoreboard VMODs Accept Accounting ACL (aclplus) ActiveDNS Akamai Connector ASN Module AWS VCL Body Access & Transformation (xbody) Brotli Cookie Plus (cookieplus) DeviceAtlas DeviceAtlas3 Digest Dynamic backends (goto) Edgestash File Format Geolocation (geoip/mmdb) Header Manipulation (headerplus) HTTP communication (http) Image JSON parsing (json) JWT Key value storage (kvstore) Least connections director (leastconn) Module to control the built-in HTTP2 transport (h2) MSE control (mse) MSE4 control (mse4) Probe Proxy ProxyV2 TLV Attribute Extraction (proxy) Pseudo Random Number Generator Purge (purge/softpurge) Real-time Status (rtstatus) Reverse DNS (resolver) Rewrite S3 VMOD Session Slicer SQLite3 Stale Standard (std) Stat (Prometheus) Strings (str) Synthetic backends (synthbackend) Tag-based invalidation (Ykey/Xkey) TCP configuration (tcp) TLS Total Encryption (crypto) Unified director object (udo) Uniform Resource Identifier (uri) Unix Socket Utilities (unix) URL Plus (urlplus) Utils Vsthrottle

Experimental ARM packages

Experimental ARM software

The Varnish Enterprise software is currently being built for the ARM CPUs in addition to the x64 CPUs, but not normally distributed to customers. The ARM effort is classified as research, which make the packages purely experimental.

Do not deploy Varnish Enterprise on production servers with ARM processors.

The software is built for ARM for two reasons:

  • Varnish Software running tests and test builds internally.
  • Customers developing VCL on their ARM based Apple computers. (Emulating the x64 environment for Varnish Enterprise on ARM based systems does not work well).

When you are granted access to the experimental ARM software, you will receive an e-mail with credentials for the software and brief installation instructions.

The e-mail will include a token that will be unique to your account, so it will be represented as TOKEN in this guide.

Installing Varnish Enterprise is basically a two step process:

  1. Configure the repository for your Linux distribution
  2. Install the software using the built in package manager

Customers who are not able to install the software should contact support@varnish-software.com.

Platforms

Varnish Enterprise for ARM is built for a limited number of platforms which are available from a special experimental repository.

We recommend one of the following distributions:

  • Debian 11.0 (bullseye)
  • Debian 12.0 (bookworm)

Note there are no supported platforms for ARM, but we are interested in knowing about any bugs in the experimental software.

Supported platforms are limited to 64bit systems with Intel or AMD processors (x64).

Repository configuration for ARM packages

Debian

Packages in our repositories are signed and distributed via HTTPS. You need to enable HTTPS support in the package manager and install our public key first:

apt-get install -y apt-transport-https
curl -L https://TOKEN:@packagecloud.io/varnishplus/experimental/gpgkey | apt-key add -

To use our Varnish Enterprise repositories, put the following in /etc/apt/sources.list.d/varnish-enterprise-6.0.list:

# be sure to replace "RELEASE" with
# "bullseye" or "bookworm", depending on your platform

# Varnish Enterprise 6.0 and VMODs
deb https://TOKEN:@packagecloud.io/varnishplus/experimental/debian/ RELEASE main

Finish by updating the apt database and installing the varnish-plus package:

apt-get update
apt-get install -y varnish-plus

Installation Notes

Transparent Huge Pages (THP)

Transparent Huge Pages is a Linux kernel feature to improve performance by more efficiently using a processors’ memory mapping hardware. This is a feature that is enabled by default on most recent Linux distributions.

Varnish does not perform well with this option enabled. As such, Transparent Huge Pages should be set to either madvice or never on any system where Varnish is operating.

The procedure to disable THP will vary based on the distribution being used. Please consult with the manual for your distribution for the correct steps to take.

The shared memory log

The shared memory log contains file which are used for communicating logs and counters to log consumers like varnishncsa and varnishlog. In some circumstances, having these files on a physical medium can create performance problems. For this reason it is strongly recommended to mount the /var/lib/varnish/ directory as a tmpfs file system.

If you choose to limit the size of the tmpfs file system, a reasonable size is three times the varnishd parameter vsl_space.


®Varnish Software, Wallingatan 12, 111 60 Stockholm, Organization nr. 556805-6203