Zap Alternatives

zap reviews and mentions

• Resource efficient Thread Pools (with Zig)
  3 projects | /r/rust | 13 Sep 2021
• Lock-free, allocation-free, efficient thread pool
  6 projects | news.ycombinator.com | 13 Sep 2021

  This actually can be at the level of a missed optimization. A run queue with a lock-shared queue amongs all the threads scales even worse than the tokio version. Sharding the run queues and changing the notification algorithm, even while keeping locks on the sharded queues improves throughput drastically.

  Tokio is an async runtime, but I don't see why being an async runtime should make it worse from a throughput perspective for a thread pool. I actually started on a Rust version [0] to test out this theory of whether async-rust was the culprit, but realized that I was being nerd-sniped [1] at this point and I should continue my Zig work instead. If you're still interested, I'm open to receiving PRs and questions on that if you want to see that in action.

  It's still correct to benchmark and compare tokio here given the scheduler I was designing was mean to be used with async tasks: a bunch of concurrent and small-executing work units. I mention this in the second paragraph of "Why Build Your Own?".

  The thread pool in the post is meant to be used to distribute I/O bound work. A friend of mine hooked up cross-platform I/O abstractions to the thread pool [2], benchmarked it against tokio to be have greater throughput and slightly worse tail latency under a local load [3]. The thread pool serves it's purpose and the quicksort benchmark is to show how schedulers behave under relatively concurrent work-loads. I could've used a benchmark with smaller tasks than the cpu-bound partition()/insertion_sort() but this worked as a common example.

  I've already mentioned why rayon isn't a good comparison: 1. It doesn't support async root concurrency. 2. scoped() waits for tasks to complete by either blocking the OS thread or using similar inline-scheduler-loop optimizations. This risks stack overflow and isn't available as a use case in other async runtimes due to primarily being a fork-join optimization.

  [0]: https://github.com/kprotty/zap/blob/blog-rust/src/thread_poo...

  [1]: https://xkcd.com/356/

  [2]: https://github.com/lithdew/hyperia

  [3]: https://gist.github.com/kprotty/5a41e9612657de00788478a7dde4...

• Question: Does Zig has work-stealing/sharing algorithm in the M:N concurrency model ?
  2 projects | /r/Zig | 5 Jul 2021

  You can implement one: https://github.com/kprotty/zap/blob/lifo/src/runtime/Pool.zig

• Tokio-uring design proposal
  4 projects | /r/rust | 8 Apr 2021

  BTW If you're interested in work stealing, i'm writing my own which has a bundle of optimizations for minimal task dispatch overhead and memory efficiency. To appease some of your criteria: yes, it's currently being used in "real world production" for an http server (although not that specific version).

• MEIO: async actors framework
  5 projects | /r/rust | 16 Feb 2021

  This is a logical fallacy. Specifically either a "Slippery Slope" or "Either/Or". You assume that fast channel implementations must have originated or have been ported to Rust and are both popular. Things like Stakker and zap are anecdotal examples of where this already isn't the case. Even so, there exists fast synchronized channels both inside and outside of async Rust. Because they aren't popular or aren't tuned to efficient runtimes doesn't mean they don't exist, which was my argument.

• A note from our sponsor - SaaSHub
  www.saashub.com | 18 Apr 2024

  SaaSHub helps you find the best software and product alternatives Learn more →