Conversation
uws WebSocket echo on uio: the RFC 6455 handshake and frame parser run in the connection's own I/O task on uio's edge-triggered event loops, one per CPU, so each message is parsed from the buffer its task read into and echoed from that task with no goroutine per connection. A read round's replies leave coalesced in one sendmsg, and a send the socket refuses is finished by the next write turn without pausing the read. Everything else is default configuration; uio v1.5.3. Subscribes to echo-ws, echo-ws-pipeline and echo-ws-limited. Validated with scripts/validate.sh (7/7 WebSocket checks).
limpo1989
requested review from
Kaliumhexacyanoferrat and
MDA2AV
as code owners
October 3, 2026 14:52
Owner
|
/benchmark --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
This branch has not been deployed
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
uio-ws — Go engine entry
This adds a WebSocket echo entry for uws, the WebSocket implementation on uio (github.com/urpc/uio, v1.5.3).
uio is a Linux/BSD network engine for Go built directly on epoll (EPOLLET) and kqueue (EV_CLEAR): one edge-triggered event loop per CPU, each connection driven by its own serialized I/O task — no goroutine per connection, no reactor-to-worker handoff. uws implements RFC 6455 framing and message rules plus RFC 7692 permessage-deflate on top of it, and passes the Autobahn test suite.
What the echo path looks like:
sendmsg(writev-style iovecs, stack-backed) instead of a syscall per reply — which is whatecho-ws-pipelineexercises.echo-ws-limiteddrives).Entry notes:
type: engine— uio is a transport engine applications are not written against; happy to move if that reads wrong.echo-ws,echo-ws-pipeline,echo-ws-limited.Pollers: runtime.NumCPU()(uio's default is 4 loops).scripts/validate.sh uio-wspasses 7/7 WebSocket checks; the entry is a 60-line echo handler, no benchmarking tricks.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.