Repository navigation
Add uWebZockets (Zig) framework entry - #1536
Merged
Merged
Conversation
Coder-Blue
requested review from
Kaliumhexacyanoferrat and
MDA2AV
as code owners
October 8, 2026 18:21
Contributor
Author
|
/benchmark -f uwebzockets --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Owner
|
Yo, can you check validations issues before I benchmark? |
Contributor
Author
Oh, sure. I'm on it. |
Coder-Blue
force-pushed
the
uwebzockets
branch
from
October 9, 2026 01:29
29db0d0 to
20d54c5
Compare
Contributor
Author
|
/benchmark -f uwebzockets --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
Contributor
Author
|
Uhm, what's up with the yellow caution sign emoji? |
Contributor
Author
|
@MDA2AV, did the validation issues from earlier disappear? I committed some new changes, but I don't see any workflow approval. |
Owner
some tests have fixed throughput, if the server cannot reach that value it will have a penalization on that test. |
Contributor
Author
Thanks for the info, sir! |
Zero-allocation shared-nothing Zig framework on libxev, serving HTTP/1.1, HTTP/2, HTTP/3 and WebSocket from bounded startup slabs. Standard configuration: plaintext clusters for h1/WS and h2c, single TLS listeners for json-tls, baseline-h2 and baseline-h3.
Flatten handlers/shared into src/main.zig to match the nilo/dusty layout and set enable_dev_log=false in the cluster configs.
Bringing all four listeners up together resets the first connections served on 8080 under startup contention; starting http last avoids the window.
Each listener is a thread in the same binary, so entrypoint.sh is gone.
Owner
|
please mark as experimental at meta.json (type) |
Contributor
Author
Fair enough, I'm on it! |
Contributor
Author
|
@MDA2AV I marked my framework as experimental just like you requested. So what should I do next? |
Owner
|
/benchmark --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
Owner
|
You should fix this.. some tests are just broken and you're not using the 64 available cpus |
Contributor
Author
Okay, I'm on it. Maybe I just accidentally hard-wired something. |
Contributor
Author
|
/benchmark -f uwebzockets --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
Contributor
Author
|
Interesting. The |
Owner
|
Well, it is quite obvious you have cpu scaling issues with anything that touches tls |
Contributor
Author
|
Confirmed. The current uWebZockets v1.8 public API only exposes TLS through a single I have corrected the entry metadata so it no longer claims physical-core pinning, and left the benchmark result intact rather than hiding the limitation. The framework remains correctly classified as experimental. I will add TLS-cluster support in the next uWebZockets release, then update the dependency and request a fresh benchmark. This PR now accurately represents the released library API and its current limitation. |
Contributor
Author
|
I have now removed the unsupported |
Contributor
Author
|
/benchmark -f uwebzockets --save |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Full log |
MDA2AV
approved these changes
Oct 14, 2026
Contributor
Author
|
Thank you for merging this PR. It was a pleasure working with you! I appreciate your time and support. I will continue hardening my framework. |
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.
Adds uWebZockets — a zero-allocation, shared-nothing Zig framework on libxev with a typed Request/Response API. Marked experimental / standard; completeness 4/4 (radix router, middleware pipeline, typed request parsing, response helpers).
Profiles: baseline, pipelined, limited-conn, json-comp, json-tls, baseline-h2c, json-h2c, baseline-h3, echo-ws (+ pipeline and limited) and the three latency profiles.
How it runs: one static binary with four listener groups:
init_https(BoringSSL), used for json-tls.init_http3(lsquic), used for baseline-h3.The released uWebZockets v1.8 public API only exposes TLS through a single application listener. Plaintext and h2c use the cluster API, but TLS-touching profiles therefore currently scale to one event loop/core. baseline-h2 is deliberately not subscribed, and its unused TCP listener has been removed: its required 1,024-connection case cannot make progress with the released TLS listener. TLS-cluster support will arrive in a follow-up uWebZockets release, after which baseline-h2 can be restored and freshly benchmarked.
Left out deliberately: baseline-h2, 8gbit, static-h2, static-h3 and static-tls. The public v1.8 TLS constructors use fixed default capacities that cannot serve the 100 KiB echo validation or the larger static assets through the framework API. There is no public timer API, database/template/gRPC/gateway support in the framework.