Skip to Content
Browse documentation

Varnish Settings

Tune every Eenos Varnish settings field with exact ranges, units, reset values and save/restart behavior.

Open Web Servers → Varnish → Varnish Settings.

All fields are required. Values below are the current reset defaults, not a recommended profile for every workload.

Memory, connections and timeouts

FieldAccepted valueReset value
Cache MemoryInteger 10–90, percentage of total RAM.20
Maximum ConnectionsInteger at least 100.600
Connection TimeoutInteger 0–20000.5
First Byte TimeoutInteger 0–20000.60
Between Bytes TimeoutInteger 0–20000.60
Send TimeoutInteger 0–20000.600
Idle Client TimeoutInteger 0–20000.5
CLI TimeoutInteger 0–20000.60
Idle Send TimeoutInteger at least 0.30

Timeout fields take bare integers. Do not enter the s suffix used by some Nginx fields. Cache Memory is calculated against system total RAM during service generation; it is not a reservation based on currently free memory.

Compression and request size

FieldAccepted valueReset value
Gzip Compression LevelInteger 0–9.9
Gzip BufferDigits followed by lowercase k, maximum 20 characters.32k
HTTP Request WorkspaceDigits followed by lowercase k, maximum 20 characters.256k

The request workspace field maps to http_req_size. These fields are not a website upload-limit configuration.

Threads and protocol

FieldAccepted valueReset value
Thread PoolsInteger 0–32.2
Minimum Threads per PoolInteger 5–10000.5
Maximum Threads per PoolInteger at least 5.10000
Thread Stack SizeDigits plus lowercase k, maximum 20 characters.64k
Thread Idle TimeoutInteger at least 10.300
Thread Queue LimitInteger at least 0.20
Thread Statistics RateInteger at least 0.10
Thread WorkspaceDigits plus lowercase k, maximum 20 characters.4k
Thread Destroy DelayInteger at least 0.2
HTTP/2 SupportEnabled or disabled, stored as +http2 or -http2.Enabled

The form validates individual bounds and suffixes. It does not comprehensively verify Varnish version compatibility, thread relationships or whether the combined resource settings are practical. A value accepted by the form is not automatically a suitable runtime value.

Allow capacity for the rest of the stack

Cache allocation and thread settings share resources with web servers, databases and applications. Preserve working values and validate the generated configuration before restarting; do not use the highest allowed values as a tuning target.

Save and apply

  1. Record the current settings.
  2. Edit the intended fields and click Save Settings.
  3. Correct validation errors and read the result.
  4. Inspect the generated service configuration, VCL and logs.
  5. Use Restart, review the confirmation and continue when ready.
  6. Verify Varnish service health and representative website/cache responses.

Saving writes preferences, regenerates the Varnish systemd service definition, requests a systemd daemon reload and regenerates default VCL. Success depends on the helper results for service generation and VCL generation. It does not automatically restart Varnish or prove the new settings work under load.

A failure can occur after preferences or configuration files have changed. Inspect the resulting state before retrying.

Reset defaults

Click Reset Defaults, review the confirmation and confirm. Reset writes the values above and attempts the same service/VCL generation steps. The current reset helper can report success even when a write or generation step fails, so reload the page and verify configuration before restarting.

Reset is not a rollback to the immediately previous save. Keep a record of custom values.

Restart and recovery

The restart action performs an actual Varnish service restart and queries its status. It is separate from saving settings. If it fails, inspect service and configuration errors, restore valid settings and verify the backend before retrying.

Demo sessions cannot perform these actions.