frameworks/node: add benchmark implementation - #1202
Open
nigrosimone wants to merge 1 commit into
Open
Conversation
nigrosimone
marked this pull request as ready for review
August 18, 2026 06:22
nigrosimone
requested review from
Kaliumhexacyanoferrat and
MDA2AV
as code owners
August 18, 2026 06:22
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.
Node was on the board only through frameworks (express, fastify, koa, nestjs, node-h3, hono-node), with no bare
node:httpline to read them against. bun, deno and go-stdlib already have one.One file, no dependencies:
http.createServer, routing by string comparison onreq.url, query parsed by hand, andzlib.gzipSyncon/jsonbecause node:http negotiates nothing.node:clusterforks one worker per core, but each worker binds 8080 withreusePort, so the kernel spreads the accepts the way bun and deno do, not the cluster round robin.Profiles are the same six as bun, deno and go-stdlib. Checked with the image on 4 cpus: 4 workers, 4 LISTEN sockets on 8080, and every endpoint the profiles use.