Re:A multithreaded fork of Redis that is faster
by lllr_finger on Monday October 07, 2019 @06:08PM
(#21186503)
Disruptor benefits from lock free access using a ring buffer. You can get amazing results with a single thread but that aspect isn't central to the pattern.
Re:A multithreaded fork of Redis that is faster
by nvarsj on Monday October 07, 2019 @05:36PM
(#21186211)
The disruptor isn’t single threaded at all. Maybe you mean it can pin a core to a consumer that just busy waits on the queue. That is a common technique used in very low latency systems when not running on a real time OS.
https://www.martinfowler.com/articles/lmax.html
I believe other (grown-up/legacy!) exchanges work the same way.
I wonder how much of the direction of concurrency research is driven by the fact that there is much more publishable work to be done in managing concurrency rather than avoiding it!