|
|
|
|
|
|
by jason_wo
1095 days ago
|
|
|
As far as I know the LMAX disrupter is a kind of queue/buffer to send data from one thread/task to another. Typically, some of the tasks run on different cores. The LMAX disruptor is designed such that there is no huge delay due to cache coherency. It is slow to sync the cache of one core to the cache of another core when both cores write to the same address in RAM. The LMAX disruptor is designed that each memory location is (mostly) written to by at most thread/core. How is the LMAX disrupter relevant for programs with 1 core? |
|
|
It is not relevant outside the problem area of needing to communicate between threads. The #1 case I use it for is MPSC where I have something like an AspNetCore/TCP frontend and a custom database / event processor / rules engine that it needs to talk to.