Repository navigation
Conversation
Add a `post` scenario that sends `POST /` with a `{"hello":"world"}`
JSON body which each server parses and echoes back. POST servers live
in benchmarks/post/ for fastify, hono, h3, koa, express, restify, hapi
and node-http.
Run it with `npm start y 100 10 40 post` and compare with
`benchmark compare -s post`. Results are written to
benchmark-results-post.json and a `# POST Benchmarks` README section;
the GET scenario's output is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Benchmark new Fastify releases as soon as they are published. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tony133
requested changes
Oct 18, 2026
| @@ -1,4 +1,5 @@ | |||
| ignore-scripts=true | |||
| min-release-age=7 | |||
| min-release-age-exclude[]=fastify | |||
Member
There was a problem hiding this comment.
Could you add a comment here with the removal date, e.g. # remove after 2026-10-20?
Member
Author
There was a problem hiding this comment.
Honestly I think we can keep excluding Fastify here?
The whole purpose of this repo is to benchmark Fastify against other frameworks, and both repos are under our control, so it would be good for the runner to be able to pick up the latest Fastify as soon as possible
But if you still think we shouldn't do it, I'm happy to add the comment
Member
There was a problem hiding this comment.
Okay, I thought it was a temporary thing; let’s see what the others think—no problem for me.
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.
Happy to announce the results of my recent performance work! It was focused mostly on cases where there is a request body. Therefore a new
simple POSTbenchmark was added.On POST, Fastify 5.10.0 was 5% slower than Hono, and 5.12.7 is 24% faster. It's pretty significant considering we're now faster than everybody else despite doing more work by default, such as protecting against prototype poisoning
I will update the website after this merges so it shows both the simple get and simple post results
More results between Fastify and Hono:
Fastify 5.12.7 vs Hono 4.13.13**: 3 rounds,
autocannon -c 100 -d 40 -p 10, Node v24.21.0, darwin arm64 (15 cores). Order alternated each round.Fastify served 18.4% more requests per second on average (+15.5% to +20.7% per round) with 16.2% lower average latency, while rejecting prototype-poisoning payloads by default.