Zix 0.4.x rc3 http#885
Conversation
|
Testing zix HTTP/1.1 scope with epoll. |
|
/benchmark -f zix |
|
👋 |
Benchmark ResultsFramework:
Full log |
|
Testing zix HTTP/1.1 scope with io_uring. |
|
/benchmark -f zix |
|
👋 |
Benchmark ResultsFramework:
Full log |
|
Picking io_uring. Proceeding correcting meta.json information. |
|
Submitting result. |
|
/benchmark -f zix --save |
|
👋 |
|
Wait, I need your opinion. Should I submit after zix-ws & zix-grpc tested? @MDA2AV Honestly not many change for zix-ws #886 and zix-grpc #887 So in zix-ws & zix-grpc I'll push and selecting io_uring dispatch model. zix 0.4.x-rc3 will reflect zix 0.4.x release. What do you think? |
Benchmark ResultsFramework:
Full log |
I can push this, it is up to you. There are no rules/checks for engine entries, values are merely informative |
|
👋 |
Description
Bump the zix entry to 0.4.x-rc3 (HTTP/1.1 scope).
Update:
Required to call from HttpArena:
/benchmark -f zix/benchmark -f zix --saveResult benchmark:
Submitting:
Important:
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.