The Rust performance book features over a dozen different profiling tools. So I’m not sure if the world needed a new Rust profiler. Still, I spent the last 6 months building hotpath-rs. In this post, I’ll describe the design decisions behind the library and share a few performance challenges I encountered while working on it. We’ll go deep into the low-level details like cache-line contention, async futures instrumentation, and decoding raw CPU traces back into Rust symbols.

Hotpath. Use to diagnose performance issues.

Excellent explainer of memory ordering

A Q

https://github.com/davidfowl/AspNetCoreDiagnosticScenarios/blob/master/AsyncGuidance.md

Last year was an important year for Async Rust, culminating in the release of async fn in traits, one of Rust’s most long-awaited language features. I’m really proud of the work and expertise the Async Working Group has put in to this effort, and for the community feedback that helped shape the release.We still have important work to do in the coming year, and setting priorities is one of the top things on my mind right now.

Trio – a friendly Python library for async concurrency and I/O - python-trio/trio: Trio – a friendly Python library for async concurrency and I/O

Emacs lisp is not multi-threaded. This library explores possibilities to work around this. It allows forms to be evaluated in a different Emacs process. This means that the executed code cannot access the current environment, and the code’s side effects cannot be used directly. There is a small overhead from starting a new process.

ActorKit provides an Objective-C implementation of asynchronous inter-thread message passing.