Repository navigation
Conversation
hatahet
requested review from
Kaliumhexacyanoferrat and
MDA2AV
as code owners
November 16, 2026 02:52
SO_REUSEPORT listener per core
hatahet
force-pushed
the
vertx-listener-per-core
branch
from
November 16, 2026 05:34
e39ac21 to
241ad44
Compare
Contributor
Author
|
/benchmark -f vertx |
Contributor
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Contributor
Benchmark ResultsFramework:
Composite score, main against this run, in the board's default view:
The results on main were measured in another session, so a few points up or down can be the machine and not the change. Full log |
A Vertx folds every server on a host:port into one listening socket, accepted on its single acceptor thread, so that thread caps new connections per second. On the 64-core host limited-conn sits at 630K req/s with 28 CPUs busy. Run one Vertx per core, each with a single event loop and one server verticle, and set setReusePort(true) on the 8080, 8081 and 8082 servers, so each core binds its own socket and the kernel spreads new connections across them. Main now exits if a deployment fails.
hatahet
force-pushed
the
vertx-listener-per-core
branch
from
November 18, 2026 02:43
241ad44 to
92f60f9
Compare
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
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
Runs one
Vertxper core, each with a single event loop and its ownSO_REUSEPORTlistener on 8080, 8081 and 8082.A single
Vertxaccepts every connection on one acceptor thread, which capslimited-conn: the published run is at 630K req/s with 28 of 64 CPUs busy.PR Commands — comment on this PR to trigger (requires collaborator approval):
/benchmark -f <framework>/benchmark -f <framework> -t <test>/benchmark -f <framework> -t <t1>,<t2>,.../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 results/spec -f <framework>specin itsmeta.json/spec -f <framework> --savesite/data/spec/(lands with the merge, like saved results)For
/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.A
/benchmarkwithout-talso runs the compliance suites, and its--savesaves their scores with the results./specruns the suites alone; without-fit runs them for every framework the PR touches. See Compliance.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.