Add to fastify benchmarks
See original GitHub issueThere are a bunch of http libs that claim to be fast. And there is a benchmark to see who is fastest.
You should add turbo-http
to the benchmarks repo and see how it measures up 😄
https://github.com/fastify/benchmarks
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Benchmarks - Fastify
Benchmarks. Leveraging our experience with Node.js performance, Fastify has been built from the ground up to be as fast as possible.
Read more >Fast and low overhead web framework fastify benchmarks.
Fast and low overhead web framework fastify benchmarks. - GitHub - fastify/benchmarks: Fast and low overhead web framework fastify benchmarks.
Read more >Performance (Fastify) - A progressive Node.js framework
However, fastify is much faster than Express, achieving almost two times better benchmarks results. A fair question is why does Nest use Express...
Read more >Fastify-benchmarks NPM - npm.io
Benchmarks ; restify, ✓, 34609.6 ; take-five, ✓, 30164.8 ; express-with-middlewares, ✓, 28750.4 ; fastify-big-json, ✓, 11256.8 ...
Read more >Reaching Ludicrous Speed with Fastify - NearForm
Fastify is a great choice to build an application where performance is a critical concern. Compared with some of the more established frameworks ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t think this is really relevant – this module is a level below a web framework – it’s essentially a replacement for
require('http').createServer()
… but even simpler than that. It’s possible the frameworks listed there could run on this instead of the built-in node.js http module, but I imagine that’s not necessarily its goal.Not relevant. This is a HTTP server, as opposed to a server framework. Aka, this replaces
require('http')
but does not replacerequire('express')
.