-
Notifications
You must be signed in to change notification settings - Fork 61
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
Would be interested in seeing some sort of benchmarks (@fastify/nextjs) #566
Comments
Transfered to |
Thanks for reporting! Would you like to send a Pull Request to address this issue? |
For sure! Anything to help push the fastify ecosystem forward! (Just gotta find the free time which I might have this weekend) |
@mcollina I did some testing of this over the weekend and can write it up when I have time... BUT it all comes down to fastify-nextjs being just as fast as the next server, tho if you are using fastify-nextjs there is a higher warmup cost than there is with just next. I did a bunch of different trials and fastify came to the conclusion that it is mostly "too close to call!" PS: I used this cool cli tool to do the testing called 'autocannon', maybe you have heard of it? |
Seems about right, it is the next server after all ;). |
EDIT: I thought I was posting this specifically on the fastify-nextjs repo.
Prerequisites
Issue
EDIT: I thought I was posting this specifically on the fastify-nextjs repo.
No issue to report. Just here to say that I would be interested in seeing some sort of benchmarks against an express custom server and/or a vanilla next app.
Food for thought!
The text was updated successfully, but these errors were encountered: