RustTokioBenchmark VS Umpire

Compare RustTokioBenchmark vs Umpire and see what are their differences.

RustTokioBenchmark

Simple benchmark comparing tokio mpsc with standard rust one (by eras)

Umpire

Combat Quest of the Millennium (by joshhansen)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
RustTokioBenchmark Umpire
1 4
0 7
- -
2.7 8.3
about 1 month ago about 1 year ago
Rust Rust
MIT License GNU General Public License v3.0 only
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

RustTokioBenchmark

Posts with mentions or reviews of RustTokioBenchmark. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-26.
  • 3 years of fulltime Rust game development, and why we're leaving Rust behind
    21 projects | news.ycombinator.com | 26 Apr 2024
    > If you ever pull up a debugger and step through an async Rust/tokio codebase, you'll get a good sense for what the overhead here we're talking about is.

    So I didn't quite do that, but the overhead was interesting to me anyway, and as I was unable to find existing benchmarks (surely they exist?), I instructed computer to create one for me: https://github.com/eras/RustTokioBenchmark

    On this wee laptop the numbers are 532 vs 6381 cpu cycles when sending a message (one way) from one async thread to another (tokio) or one kernel thread to another (std::mpsc), when limited to one CPU. (It's limited to one CPU as rdtscp numbers are not comparable between different CPUs; I suppose pinning both threads to their own CPUs and actually measuring end-to-end delay would solve that, but this is what I have now.)

    So this was eye-opening to me, as I expected tokio to be even faster! But still, it's 10x as fast as the thread-based method.. Straight up callback would still be a lot faster, of course, but it will affect the way you structure your code.

    Improvements to methodology accepted via pull requests :).

Umpire

Posts with mentions or reviews of Umpire. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-26.

What are some alternatives?

When comparing RustTokioBenchmark and Umpire you can also consider the following projects:

ntfs - An implementation of the NTFS filesystem in a Rust crate, usable from firmware level up to user-mode.

lxd-snapper - LXD snapshots, automated

mini-me - Inline multiline text-editor/prompt written in Rust.

xwin - A utility for downloading and packaging the Microsoft CRT headers and libraries, and Windows SDK headers and libraries needed for compiling and linking programs targeting Windows.

tui-realm - 👑 tui-rs framework to build stateful applications with a React/Elm inspired approach

wasm-bindgen-serde-example

sciter - Sciter: the Embeddable HTML/CSS/JS engine for modern UI development

desktop-streaming - WebRTC desktop streamer using Rust

windows-rs - Rust for Windows

music-vibes - Desktop app for translating audio output into vibrations

kobold - Easy declarative web interfaces.

open_safety - An application to assist with securing script execution