vanilla: split into vanilla-epoll and vanilla-io_uring#866
Open
enghitalo wants to merge 2 commits into
Open
Conversation
Replace the single `vanilla` framework entry with two engine variants that exercise the server's two Linux I/O backends: - vanilla-epoll — io_multiplexing: .epoll (engine: epoll) - vanilla-io_uring — io_multiplexing: .io_uring (engine: io_uring) Both share identical handlers, profiles, Dockerfile, and the pinned enghitalo/vanilla module; the only functional difference is the one ServerConfig backend line in main.v. Setting `engine: io_uring` in meta.json makes the harness run that variant with `--security-opt seccomp=unconfined` and `--ulimit memlock=-1:-1` (scripts/run.sh). site/data/frameworks.json regenerated via scripts/rebuild_site_data.py. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The vanilla server's RequestHandler contract changed (io_uring rewrite, enghitalo/vanilla@c26bbbd): it is now `fn (req []u8, fd int, mut out []u8) !` — the handler APPENDS the raw response to the connection's persistent write buffer `out` instead of returning `[]u8`. The Dockerfile clones vanilla `main` unpinned, so both variants failed to build against the new API: main.v:598: error: cannot assign to field `request_handler`: expected `fn ([]u8, int, mut []u8) !`, not `fn ([]u8, int) ![]u8` Append `handle()`'s result into `out`; this also batches correctly for pipelined requests (each response is appended and flushed in one send). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Author
|
/benchmark -f vanilla-epoll |
Contributor
|
👋 |
Contributor
Author
|
/benchmark -f vanilla-io_uring |
Contributor
|
👋 |
Contributor
Benchmark ResultsFramework:
Full log |
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.
What
Replaces the single
vanillaframework entry with two engine variants that exercise the server's two Linux I/O backends:enginemain.vbackendvanilla-epollepollio_multiplexing: .epollvanilla-io_uringio_uringio_multiplexing: .io_uringWhy
vanilla ships both an epoll and an io_uring backend, selected at runtime via one
ServerConfigline. Splitting the entry lets the leaderboard compare the two backends head-to-head under identical handlers.Details
Dockerfile, and the pinnedenghitalo/vanillamodule — the only functional difference is the backend line inmain.v.engine: io_uringinmeta.jsonmakes the harness run that variant with--security-opt seccomp=unconfinedand--ulimit memlock=-1:-1automatically (scripts/run.sh).site/data/frameworks.jsonregenerated viascripts/rebuild_site_data.py(frameworks-only) — clean swap, no other entries touched.site/data/*-NNN.jsonleft untouched (immutable run snapshots).🤖 Generated with Claude Code