Async cancellation: a case study of pub-sub in mini-redis

This page summarizes the projects mentioned and recommended in the original post on /r/rust

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • futures-rs

    Zero-cost asynchronous programming in Rust

  • Is this still true after it switched to using FuturesOrdered?

  • moro

    Experiments with structured concurrency in Rust

  • I see. Being single-threaded would just make it cheaper to synchronize / borrow the state mutably. So the root of the problem seems to be select? I'm looking forward to see how moro will help then :)

  • 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.

    InfluxDB logo
  • retina

    High-level RTSP multimedia streaming library, in Rust (by scottlamb)

  • I suspected exactly that in this issue in one of my libraries, but when I actually looked with strace, I didn't see many syscalls returning EWOULDBLOCK. So then after that measurement, my new theory was that e.g. tokio::net::{Udp,Tcp}Socket would skip actually issuing the syscall if the mio layer hasn't returned availability since the last poll. Not true? Maybe I need to run my experiment again...

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts