You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, congrats for these nice & useful benchmarks !
I made a very simple benchmark here with fastify vs Express and found some intereresting data : see fastify/fastify#178 for the background.
The important point is : size of payload matters : with a big JSON payload, json stringification becomes the bottleneck, and fastify matches Express performance only if a schema is applied in fastify route, see fastify/fastify#178 (comment)
I would be glad to send a PR to add a new route in the tests, in order to test
a bigger payload, or you can directly copy the test data I used in my benchmark if you prefer !
The text was updated successfully, but these errors were encountered:
@abenhamdine I would suggest using more than 1 tool for benchmarking as well because during my prev experience some of them tend to show variance b/w themselves as well as their versions too.
@abenhamdine -Better late than never, right?
In the next couple of days I will get some big payloads into the tests and make sure they get benchmarked properly. I will keep you posted.
Hello,
First, congrats for these nice & useful benchmarks !
I made a very simple benchmark here with fastify vs Express and found some intereresting data : see fastify/fastify#178 for the background.
The important point is : size of payload matters : with a big JSON payload, json stringification becomes the bottleneck, and fastify matches Express performance only if a schema is applied in fastify route, see fastify/fastify#178 (comment)
I would be glad to send a PR to add a new route in the tests, in order to test
a bigger payload, or you can directly copy the test data I used in my benchmark if you prefer !
The text was updated successfully, but these errors were encountered: