the-benchmarker /web-frameworks
Which is the fastest web framework?
★ 7,096⑂ 750👁 138⑃ 9,042● 1,259▤ 15
7,096
stars
750
forks
138
watchers
9,042
prs
1,259
issues
15
releases
README
🚀 Web Frameworks Benchmark
A community-maintained, reproducible comparison of backend web frameworks
Explore the results · Add a framework · Report a problem · Join the discussion
From established full-stack platforms to small HTTP routers, this repository puts hundreds of implementations behind the same tiny API and runs them in isolated containers. Today, it makes a focused part of web-stack performance easier to measure, reproduce, and discuss. The longer-term goal is a comprehensive, evidence-based guide that helps businesses choose a backend framework—not merely a leaderboard that declares one universal winner.
[!IMPORTANT]
These are minimal HTTP throughput and latency tests, not a substitute for profiling a production application. Framework features, maintainability, ecosystem, security, database access, and your real workload all matter.
🧪 Benchmark contract
Every implementation is expected to listen on port 3000 and provide the same responses:
| Method | Route | Expected status | Expected body |
|:--|:--|:--:|:--|
| GET | / | 2xx | Empty |
| GET | /user/:id | 2xx | The id path parameter |
| POST | /user | 2xx | Empty |
Before an implementation is benchmarked, the shared RSpec contract verifies these routes. The default generated benchmark runs GET / for 15 seconds using zrk --closed and keep-alive, and records a JSON report. Concurrency and routes are configurable.
Collected fields include requests per second, total data received, run duration, and the p50, p75, p90, and p99 latency percentiles. Benchmark configuration is generated from three YAML layers:
text
config.yaml provider and global settings
/config.yaml language image, runtime, and engine settings
//config.yaml
framework version, files, command, and overrides
📊 Results
The latest published results are available on the Web Frameworks Benchmark dashboard. Each result should be read in the context of its framework version, runtime or server variant, concurrency, benchmark revision, and hardware.
For a fair interpretation:
- compare runs produced by the same benchmark revision and machine;
- check the selected runtime/server variant, not only the framework name;
- treat small differences as noise until repeated;
- do not extrapolate this minimal API test to database-heavy or full application workloads.
🗺️ Roadmap
The project is evolving from a focused HTTP performance benchmark into a broader decision-support guide for organizations choosing a backend framework. The intended presentation is inspired by the clarity of quadrant-based market analysis, but the evaluation model will be designed specifically for backend frameworks and backed by transparent, reproducible evidence. This project is independent and is not affiliated with or endorsed by Gartner.
+ [ ] ⚡ Use a modern load generator, please follow discussion in https://github.com/the-benchmarker/web-frameworks/discussions/8088
+ [ ] 🔧 Optimize iTop issues
#1728More realistic implementation33 comments · 2019-08-25#8116Are we testing real-world frameworks?25 comments · 2025-01-03#7732Create new types of tests19 comments · 2024-09-07#3803Most of real-life frameworks use I/O layers. Shouldn't they be here as well?19 comments · 2021-01-19#3108Roadmap 🚀19 comments · 2020-07-07#31Add resources consumption16 comments · 2017-05-09#441vertx java framework14 comments · 2018-10-18#1148Force id to be numerical13 comments · 2019-03-31
Discussions
#10226Unable to load environment variables from my rust framework.1 comments · 2026-11-06#10110How often website is updated.2 comments · 2026-10-24#9784Memory usage tracking2 comments · 2026-09-14#9332Maravel PHP Framework qualifies for your benchmark?1 comments · 2026-05-12#9041Multiple Zig versions2 comments · 2026-01-28#8093Change scenario10 comments · 2024-12-29#8088Using an accurate benchmark tool10 comments · 2024-12-28#7907Keeping various versions for a framework1 comments · 2024-10-29
Latest release
2018.9.26 2018.9.26 2018-09-26New frameworks + Quart A python web framework 351 388 @waghanza @pgjones + Beego A go web framework 386 @GNURub + Prism A crystal web framework 340 342 @vladfaust @waghanza + http4s A scala web framework 359 356 @mfirry @waghanza + AIOHttp A python web framework 350 @greed2411 + Bottle A python web framework 343 @greed2411 @waghanza Update + Fastify Update to 1.12 362 391 @waghanza + Polka Update to 0.5 374 375 383 @waghanza + Kitura Update to 2.5 385 @waghanza + Tornado Update to 5.1 380 @waghanza + Django Update to 2.1 370 @waghanza + Sanic Update to 0.8 371 @waghanza