Comments (5)
commented on May 23, 2024
You can also try playing around with this benchmark: https://github.com/stjepang/minihttp
I wonder if the difference in performance in debug mode was simply due to hyper being more tightly integrated with tokio.
from smol.
fundon
commented on May 23, 2024
I updated benchmark results. https://github.com/fundon/smol-tokio-hyper-benchmarks
from smol.
fundon
commented on May 23, 2024
@stjepang It's clear to me now that tokio and hyper should have specialized adaptations or that they have a best practice for working together.
Thank you so much for your help!
tokio
λ autocannon 127.0.0.1:8080
Running 10s test @ http://127.0.0.1:8080
10 connections
┌─────────┬──────┬──────┬───────┬──────┬─────────┬─────────┬─────────┐
│ Stat │ 2.5% │ 50% │ 97.5% │ 99% │ Avg │ Stdev │ Max │
├─────────┼──────┼──────┼───────┼──────┼─────────┼─────────┼─────────┤
│ Latency │ 0 ms │ 0 ms │ 0 ms │ 0 ms │ 0.01 ms │ 0.06 ms │ 6.11 ms │
└─────────┴──────┴──────┴───────┴──────┴─────────┴─────────┴─────────┘
┌───────────┬─────────┬─────────┬─────────┬─────────┬──────────┬─────────┬─────────┐
│ Stat │ 1% │ 2.5% │ 50% │ 97.5% │ Avg │ Stdev │ Min │
├───────────┼─────────┼─────────┼─────────┼─────────┼──────────┼─────────┼─────────┤
│ Req/Sec │ 45695 │ 45695 │ 49215 │ 53631 │ 49560.73 │ 1994.12 │ 45690 │
├───────────┼─────────┼─────────┼─────────┼─────────┼──────────┼─────────┼─────────┤
│ Bytes/Sec │ 5.89 MB │ 5.89 MB │ 6.35 MB │ 6.92 MB │ 6.39 MB │ 257 kB │ 5.89 MB │
└───────────┴─────────┴─────────┴─────────┴─────────┴──────────┴─────────┴─────────┘
Req/Bytes counts sampled once per second.
545k requests in 11.04s, 70.3 MB read
smol
λ autocannon 127.0.0.1:8080
Running 10s test @ http://127.0.0.1:8080
10 connections
┌─────────┬──────┬──────┬───────┬──────┬─────────┬─────────┬─────────┐
│ Stat │ 2.5% │ 50% │ 97.5% │ 99% │ Avg │ Stdev │ Max │
├─────────┼──────┼──────┼───────┼──────┼─────────┼─────────┼─────────┤
│ Latency │ 0 ms │ 0 ms │ 0 ms │ 0 ms │ 0.01 ms │ 0.06 ms │ 6.19 ms │
└─────────┴──────┴──────┴───────┴──────┴─────────┴─────────┴─────────┘
┌───────────┬─────────┬─────────┬─────────┬────────┬──────────┬─────────┬─────────┐
│ Stat │ 1% │ 2.5% │ 50% │ 97.5% │ Avg │ Stdev │ Min │
├───────────┼─────────┼─────────┼─────────┼────────┼──────────┼─────────┼─────────┤
│ Req/Sec │ 47743 │ 47743 │ 51423 │ 52703 │ 50631.28 │ 1524.76 │ 47718 │
├───────────┼─────────┼─────────┼─────────┼────────┼──────────┼─────────┼─────────┤
│ Bytes/Sec │ 6.16 MB │ 6.16 MB │ 6.63 MB │ 6.8 MB │ 6.53 MB │ 197 kB │ 6.16 MB │
└───────────┴─────────┴─────────┴─────────┴────────┴──────────┴─────────┴─────────┘
Req/Bytes counts sampled once per second.
557k requests in 11.04s, 71.9 MB read
from smol.
commented on May 23, 2024
@fundon The numbers above are with multithreaded or singlethreaded smol and tokio?
from smol.
fundon
commented on May 23, 2024
multithreaded and debug mode
from smol.
Related Issues (20)
- Parallel async read and write example
- async-net add TcpSocket? HOT 1
- It's not clear how to use Executor instead of smol::spawn HOT 1
- smol violates API guidelines' "C-STABLE" HOT 2
- TLS example should use `async_tls` instead of `async-native-tls`
- RUSTSEC-2021-0060: `aes-soft` has been merged into the `aes` crate HOT 1
- RUSTSEC-2021-0059: `aesni` has been merged into the `aes` crate HOT 1
- RUSTSEC-2021-0064: `cpuid-bool` has been renamed to `cpufeatures` HOT 1
- RUSTSEC-2020-0056: stdweb is unmaintained HOT 1
- RUSTSEC-2018-0017: `tempdir` crate has been deprecated; use `tempfile` instead HOT 1
- smol::spawn: BrokenPipe io::copy failed
- Panic: "There is no reactor running, must be called from the context of a Tokio 1.x runtime" HOT 3
- Give smol-rs a logo/mascot HOT 3
- Tracking issue for potentially useful features in future Rust versions HOT 11
- Tracking issue for smol v2.0.0 HOT 9
- Failing to check for closed socket causes future to spin, hogging executor thread HOT 2
- Should we expose event-listener in this crate? HOT 3
- concurrent futures combinators with smol HOT 1
- Figure out a way to race multiple futures in smol HOT 5
- Destructors aren't run for detached tasks HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from smol.