Repository navigation
Maintain public benchmarks #21
Description
There are some well-known public benchmarks comparing Express with other Node.js web servers. However, some implementations of Express used in these benchmarks are outdated â they rely on old versions of Node.js and Express itself, which results in unfairly poor performance outcomes.
I believe the Perf Working Group could help maintain and update these benchmarks to better reflect Express's actual performance and promote more accurate results.
Here are some of the benchmarks Iâm referring to:
Activity
[-]Mantain public benchmarks[/-][+]Maintain public benchmarks[/+]wesleytodd commentedon Jul 9, 2025
@cesco69 I added this to our next meeting agenda. If you can attend to speak a bit to the goal and idea that would be awesome. #27
jonchurch commentedon Jul 23, 2025
Fixing existing benchmarks is low on my prio list here, but it would definitely be good contributions!
cesco69 commentedon Jul 24, 2025
eg. https://www.techempower.com/benchmarks/ use Express v4 on Node 20, Express 5 on Node 24 is 3x faster
wesleytodd commentedon Jul 26, 2025
Yeah, I think I agree on a priority ranking here putting this below our own internal needs. This is one of the nice things in OSS, if you (@cesco69) are interested in leading this effort I think we would happily back you in helping get those updated. Maybe if you want to reach out to them either via a PR or something else we can use this issue to track some update requests?
wesleytodd commentedon Aug 6, 2025
Just removing the agenda label because we don't have more to discuss for now. It needs a volunteer to champion but for the folks in the group this is lower priority at the moment.
nigrosimone commentedon Dec 31, 2025
Hi Guys,
I have update Express to v5 and NodeJS to v24 in https://www.techempower.com/benchmarks/ by this PR TechEmpower/FrameworkBenchmarks#10477
Benchmark results are usually published at the beginning of the year.
The others are already updated to v5
GroophyLifefor commentedon Dec 31, 2025
Awesome work sir ðŦĄ
nigrosimone commentedon Jan 2, 2026
I have also optimized some slower/poor implementation in
nigrosimone commentedon Jan 5, 2026
While optimizing the benchmarks I found some slow parts related to routing that can be optimized
waghanza commentedon Jan 6, 2026
Thanks for this discussion guys. Maintainer of the firstly listed project.
Will be awesome to have some contributions.
Please note that the project is not only about performance, but all indicators of a production app (performance, ressources consumption, security...).
I'm not specialized in all languages in this project (actually about 17), so feel free to take a look and contribute.
And also, let me know id you want to be notified when their is any update of express (or any other framework)
nigrosimone commentedon Jan 6, 2026
I have closed the-benchmarker/web-frameworks#9014 because don't mach the scope of @waghanza benchmark, use res.end instead of res.send only for avoid express's overhead (more performance, but poor security)
efekrskl commentedon Jan 8, 2026
I just bumped the Node version in fastify/benchmarks to the current Node LTS (v24), and the Express req/s went up from ~9k to ~27k. That's insane!
nigrosimone commentedon Jan 8, 2026
Yep. But all framework benefit of 3x from node 24
efekrskl commentedon Jan 8, 2026
I'm not sure if that's true, at least not according to this benchmark.