Add roadrunner framework#716
Merged
Merged
Conversation
williamthome
requested review from
Kaliumhexacyanoferrat and
MDA2AV
as code owners
Owner
|
/benchmark -f roadrunner |
Contributor
|
👋 |
Contributor
Benchmark ResultsFramework:
Full log |
Owner
|
/benchmark -f roadrunner --save |
Contributor
|
👋 |
Contributor
|
|
The auto-buffering path can't handle 128 concurrent 20 MB POSTs
regardless of how the conn accumulates bytes (peak RSS >8 GiB, 0
req/s under the validator's load). All four listeners now declare
`body_buffering => manual`; the upload handler drains the body in
64 KB chunks via `roadrunner_req:read_body/2 #{length => 65536}`.
benchmark-lite roadrunner upload (128c, 5s × 3):
| stage | req/s | RSS |
|---|---:|---:|
| auto (pre-fix) | 749 | 4.1 GiB |
| auto (post roadrunner fixes) | 0 | 8.4 GiB |
| manual stream | 1566 | 399 MiB |
Roadrunner SHA bumped to a8596b786eff for the iodata body field.
Listener opts reshaped in v0.1.0: h2c => enabled becomes protocols => [http2] on plain TCP; TLS h2 uses protocols => [http2, http1] with auto-derived alpn_preferred_protocols. OTP 29 GA dropped the rebar3 TLS-1.2 workaround needed for RC3 + Fastly, so retire config/rebar3_ssl.config + ERL_FLAGS and bump the Dockerfile base to erlang:29.0-alpine. Add 8082 to EXPOSE. README: move baseline-h2c, json-h2c, static-h2 from deferred to covered (19/28) to match meta.json and the live listeners.
The file's own header marked it as a local snapshot to be removed before opening the PR; clearing it out so the merged contribution doesn't ship a stale benchmark capture.
The branch added the framework dir and meta.json but never wired the site-level registry, so the entry wouldn't render in the UI even after benchmark CI populates the per-profile result files.
williamthome
force-pushed
the
feat/add-roadrunner-framework
branch
from
d9dfda3 to
3ea3a09
Compare
Contributor
Author
|
@MDA2AV rebased onto main |
Owner
|
/benchmark -f roadrunner --save |
Contributor
|
👋 |
Contributor
|
|
Owner
|
nevermind Ill just run it directly |
MDA2AV
approved these changes
May 18, 2026
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
2 participants
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
roadrunneris a pure-Erlang HTTP/1.1, HTTP/2, and WebSocket server from the Arizona framework, pinned to hex0.1.0on OTP 29.PR Commands — comment on this PR to trigger (requires collaborator approval):
/benchmark -f <framework>/benchmark -f <framework> -t <test>/benchmark -f <framework> --saveAlways specify
-f <framework>. Results are automatically compared against the current leaderboard.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.