varnish: implement static-tls, baseline-h2c, upload - #1422
Draft
gquintard wants to merge 4 commits into
Draft
Conversation
- static-tls: second TLS frontend on :8081 reusing the existing vmod-fileserver /static/* route. - baseline-h2c: second cleartext listener on :8082; feature=+http2 already negotiates h2 prior-knowledge on it. - upload: new CountingWriter + httparena.upload_count() vmod function, reads and discards the body without buffering it.
gquintard
requested review from
Kaliumhexacyanoferrat and
MDA2AV
as code owners
September 1, 2026 21:17
Contributor
|
👋 Heads up! This PR modifies the following frameworks:
|
upload was unscored and replaced by 8gbit upstream (MDA2AV#1373, MDA2AV#1382) before this branch's meta.json change landed, so CI correctly rejected it as an unknown profile. Removes the vmod's CountingWriter/upload_count and the /upload VCL route along with it. latency-10k already exists in the shared profile registry and drives the same GET /baseline11 baseline already validates, so subscribing costs no new code, same as latency-1m.
default.vcl had no vcl_backend_response, so fetched objects held Varnish's default TTL (~120s) — well past the 30s staleness window infrastructure entries get. static-tls's fileserver.root() backend is otherwise identical to static-h2's, but only static-tls's suite runs the staleness probe, so this was the first place it surfaced. 5s keeps this a real cache (repeat requests still served from memory) while revalidating against the mounted directory inside the probe's window.
Contributor
Author
|
/benchmark -f varnish --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
gquintard
marked this pull request as draft
September 2, 2026 05:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
PR Commands — comment on this PR to trigger (requires collaborator approval):
/benchmark -f <framework>/benchmark -f <framework> -t <test>/benchmark -f <framework> --save/benchmark -f <framework> -t <test> --save/benchmark -f <framework> --compare <other>/benchmark-multiple -f <fw1>,<fw2>,...-tand--savetoo; saved results land in a single commit/benchmark-multiple --save-fneeded: benchmark and save every framework the PR touches/benchmark-test -t <test><test>and save the resultsFor
/benchmark, always specify-f <framework>; the flags combine in any order. Results come back as a comment with a per-profile table of RPS, p99, CPU and memory — one table per framework on multi runs. A new benchmark comment while a run is in flight queues behind it (one deep) instead of cancelling it. For multi-framework PRs (dependency bumps, same-language refactors) prefer/benchmark-multiple, which runs everything in a single job and commits all saved results together, so no run overwrites another.--compareworks on single-framework runs only.What the deltas are measured against. By default, this framework's own results published on
main- answering "did this change help?". When you are tuning a variant or a successor entry,--comparere-bases them on another entry instead:The reply states which baseline it used, and profiles the other framework does not run show
n/arather than a delta.Run benchmarks locally
You can validate and benchmark your framework locally with the lite script — no CPU pinning, fixed connection counts, all load generators run in Docker.
Requirements: Docker Engine on Linux. Load generators (gcannon, h2load, h2load-h3, wrk) are built as self-contained Docker images on first run.