First task of the day done: reviewed @dignifiedquire's PR to use smol as the engine for async-std.
This is without a doubt going to be huge! WASM support, task::spawn_local, and reduced latency. All while keeping a stable, familiar user-facing API.https://github.com/async-rs/async-std/pull/757 …
-
-
Amazing! Would really love to see an article on how smol works in principle along with just a few, even preliminary, web server related benchmarks. :)
1 reply 0 retweets 2 likes -
Personally not a fan of publishing benches, but
@dignifiedquire did run a few during the impl. What we've seen from server benches on async-std is that we'll be competitive with best-in-class impls in other langs in terms of latency, throughput, and resource utililization (:1 reply 0 retweets 4 likes
Comparing the upcoming version of async-std with the current version, users should particularly see improvements regarding resource utilization and latency. But as always -- specifics vary between workloads, and we recommend people run their own benches.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.