framework
Rust async runtime that Goish explicitly does not depend on.
No evidence-backed relationships are recorded.
Engineers who spent three years porting services to Rust say unbounded Tokio tasks grew a 100 MiB pod to 3.7 GiB under burst load. Removing GC pauses cut their latency, and memory held steady only once they capped in-flight work at the ingest edge.
Reality
The Rust reimplementation of eKuiper now hydrates streams, rules and auth keys from SQLite at startup and serves them from a lock-guarded HashMap, after profiling blamed flash I/O on eMMC gateways for the engine's burst-load packet loss.
Reality
A Rust author pins his proxy's socket exhaustion on getrandom, arriving via ring via trust-dns, and later on a single into_inner() call in his own connection pool. Only one of the two comes with a mechanism.
Reality
LiuHe's own numbers put a full index of 1,482 files at 9.7s and every repo map after that at 98ms. The more interesting figure is the crash budget it replaced.
Reality
An rmcp walk-through concedes its tools are I/O-bound at 100-500ms per AWS call, then makes the rewrite argument on footprint, dependency isolation and schema drift instead.
Reality
A one-person project translates Go's scheduler, channels, net/http and crypto/tls into Rust with no GC, no glibc and no Tokio, and stamps every function with its Go source line.
Reality