We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/fastify/fastify
Is this out of date or accurate? Can anything be done to make this package not be a performance killer?
The text was updated successfully, but these errors were encountered:
Also interested in this subject. My wild guess culprit could be url / url-pattern as it's relying on some [slow] regex.
Sorry, something went wrong.
Tried https://github.com/petkaantonov/urlparser Some benchmarks:
With node url:
url
Both are awesome but micro is 67.92% faster than microrouter • micro request average is 13524 • microrouter request average is 8054 ✨ Done in 4.86s.
With fast-url-parser:
fast-url-parser
Both are awesome but micro is 51.92% faster than microrouter • micro request average is 14260 • microrouter request average is 9386.4 ✨ Done in 3.48s.
So there are some improvements as you can see. I can send PR ( using fastify benchmarks https://github.com/fastify/benchmarks )
Looks like should be possible to boost more performance refactoring url-pattern
url-pattern
No branches or pull requests
https://github.com/fastify/fastify
Is this out of date or accurate? Can anything be done to make this package not be a performance killer?
The text was updated successfully, but these errors were encountered: