Add zix http and grpc#810
Merged
Merged
Conversation
Owner
|
/benchmark -f zix |
Contributor
|
👋 |
Contributor
Benchmark ResultsFramework:
Full log |
MDA2AV
approved these changes
Jun 7, 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.
ZIX (Zero sIX)
Add zix v0.2.2 as two entries.
frameworks/zix
Zix HTTP/1.1, subscribes to:
baseline,pipelined,limited-conn,json,upload,static,echo-wsvalidate.sh: 31 passed, 0 failed
Note: gcannon tests report 0 req/s locally — gcannon requires
RLIMIT_MEMLOCK=unlimited(io_uring locked-memory limit). wrk-basedtests (static) work correctly at ~80k req/s. May differ from actual test.
frameworks/zix-grpc
Zix gRPC h2c, subscribes to:
unary-grpc,stream-grpcLocal benchmark (native h2load/ghz, not Docker):
validate.sh: 0 passed, 0 failed (gRPC server has no HTTP/1.1 probe endpoint, startup check passes, no validate tests defined)
Why
engineBoth entries are typed
enginebecause zix exposes raw HTTP/1.1 andgRPC h2c mechanics with minimal abstraction: no TLS, no built-in
middleware, no database integration, no compression, no auth. The
framework is closer to a hand-rolled epoll server than a batteries-included
production stack.
If the PR considers the test coverage or feature set more
appropriate for a different type (
production,tuned, etc.),feel free to suggest, happy to update the meta.json accordingly.