-
Notifications
You must be signed in to change notification settings - Fork 646
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add hapi (Node) #233
Comments
@waghanza great work mate! I see the PR is merged but no docs were added, nor a place in the benchmarks. These would be extremely helpful as well =) |
Isn't Hapi like the slowest framework around? |
@aichholzer that is the point =) |
@armand1m Thanks. Good catch ;-) due to intense work 😛
@aichholzer We will see ... the next release will no be production-ready, the next after will (but I do not know when I will have the time to do so) PS : Some previous results
|
How did Fastify get almost 10K req/s ahead of the rest? - Does not seem to be realistic. |
If you are running on a multi-core server, then you should enable It will increase it's performance (and throughput) by almost 200% percent, hence blowing the socks off the other contenders, although it will probably not be a fair competition... 🙈 |
@aichholzer 😛 I'm sure you'll be impatient to compete ^^ Feel free to PS : All |
PM2 will run on multi-cores if enabled and if the server supports it. I will try to get a PR across. Still curious on Fastify's performance gains. |
@aichholzer sending those result was a (gentle) provocation 😛. Above results are garbage / draft |
🤣 |
https://github.com/hapijs/hapi
The text was updated successfully, but these errors were encountered: