-
Notifications
You must be signed in to change notification settings - Fork 187
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
Add performance benchmark #47
Comments
Feel free to create a script that runs & records the benchmarks :) |
1 example: |
@mitchtbaum Please, notice that it was the other way around on my laptop: 245k req/s for Thruster vs 208k req/s for Actix-web, but I cannot believe the numbers as Python-based framework Vibora reaches 328k req/s which is complete nonsense! I don't understand what is going on... |
@frol Well, python also has japroto which cloud be a lot faster than Vibora since most parts are written in C. |
@pickfire @frol @naturallymitchell I'm doing the same thing (mesuring performance) in https://github.com/the-benchmarker/web-frameworks We could centralize our efforts ❤️ |
@waghanza There is also https://github.com/TechEmpower/FrameworkBenchmarks which may contains even more |
Sure, but a little bit different. In short, my value is to take care of having up-to-date versions of frameworks and languages |
👍 |
There is also https://github.com/rousan/rust-web-frameworks-benchmark |
Benchmarks can be easily done with the examples that they included in the project source itself.
For most of the frameworks, we could just use (except a few weird crates that name it differently such as
hello_world
orhello
):And then on another terminal:
If we could, we could bump each repository and let them have a standard name
hello-world
with a standard port to simplifies things in the future. What I learned from benchmarking ~7 different frameworks? I am surprised thatactix_web
was the fastest even when lower level frameworks (hyper
,tokio-tinyhttp
,tokio-minihttp
) is included and does not have routing.By the way, it would be great if this was included in http://arewewebyet.org
The text was updated successfully, but these errors were encountered: