Add static-tls profile: 20-file static serving over HTTP/1.1 + TLS - #1087
Merged
Conversation
Owner
Author
|
/benchmark -f genhttp-11 -t static-tls --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
|
|
Contributor
|
👋 Heads up! This PR modifies the following frameworks:
|
Exactly the static workload transported over TLS on :8081 (the json-tls port), driven by wrk with the same static-rotate.lua. Scored at 1024/4096/6800 connections like static. - profiles.sh: spec + order + wrk dispatch for the static-tls endpoint - wrk adapter: https://localhost:8081 with the existing rotation script - framework.sh: TLS readiness probe on /static/reset.css - validate.sh: full static check suite over TLS (ALPN http/1.1 negotiation, Content-Types, 20 file sizes, compression, 404), and static-tls now triggers the 8081 port mapping + static mount - docs: implementation/validation/index pages + isolated section card - catalog: scored, not engine-scored (mirrors static) Also subscribes genhttp-11-ioxide to the new test. Validation passes except vendor.js (300 KB): ioxide.tls 0.0.17 hangs on TLS responses larger than exactly 256 KB (262,144 B verified by bisection; plaintext unaffected, no configurable buffer in TlsOptions). Needs an engine fix before this framework's static-tls results can land. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
genhttp-11's standard TLS stack (SslStream via X509 PEM binding on :8081, shared handler tree with Assets.From) passes the full static-tls validation suite — 56/56 checks including the 300 KB vendor.js that trips the ioxide.tls 256 KB write-path hang. genhttp-11-ioxide's subscription is withdrawn until the engine fix lands. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
MDA2AV
force-pushed
the
feat/static-tls-profile
branch
from
August 7, 2026 19:45
52ad005 to
402f83c
Compare
Owner
Author
|
/benchmark -f genhttp-11 -t static-tls --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
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.
Exactly the static workload transported over TLS on :8081 (the json-tls port), driven by wrk with the same static-rotate.lua. Scored at 1024/4096/6800 connections like static.
Also subscribes genhttp-11-ioxide to the new test. Validation passes except vendor.js (300 KB): ioxide.tls 0.0.17 hangs on TLS responses larger than exactly 256 KB (262,144 B verified by bisection; plaintext unaffected, no configurable buffer in TlsOptions). Needs an engine fix before this framework's static-tls results can land.
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, ghz) are built as self-contained Docker images on first run.