Can I select multiple receivers concurrently, similar to a select in Linux?
Readit Newstontinton commented on Crossfire: High-performance lockless spsc/mpsc/mpmc channels for Rust github.com/frostyplanet/c... · Posted by u/0x1997
tontinton commented on Search logs faster than Sonic – Log search engine internals blog.vegasecurity.com/pos... · Posted by u/tontinton
Learn about the data structures & algorithms that make up modern log search engines like Elasticsearch.
> Running a thread per client is famously known as The C10K Problem.
Gonna have to be that guy: the C10K problem was "how to serve 10000 clients from a single server" specifically in the 2000ish time-frame. The article links to the C10K problem page, which discusses the tradeoffs involved in at least five high-level strategies[1], only one of which is the strategy of running a thread per client [2].
[1] http://kegel.com/c10k.html#strategies [2] http://kegel.com/c10k.html#threaded
You're right, I'll fix it in the post.
Thanks!
Excellent overview of scheduling with code examples and animations.
One minor correction about Erlang is that that scheduler doesn't get invoked just on function calls. It will be invoked as soon as the lightweight process consumes a certain number of allowed operations. So even if you have one huge function that never calls others, just computes something, it will still consume operations and will be preempted. Some internal C utility functions also consume some virtual number of ops as well and may yield.
Yeah I might have been wrong, simply went with https://blog.stenmans.org/theBeamBook/#_reductions
Now that I reread that section, it also depends on whether you call a BIF or not, I'll think about how to phrase that better in the blog post.
Thanks!