Willy Tarreau c7bd7a68e4 OPTIM: ring: have only one thread at a time wake up all readers ... It's inefficient and counter-productive that each ring writer iterates over all readers to wake them up. Let's just have one in charge of this, it strongly limits contention. The only thing is that since the thread is iterating over a list, we want to be sure that if the first readers have already completed their job, they will be woken up again. For this we keep a counter of messages delivered after the wakeup started, and the waking thread will check it before going back to sleep. In order to avoid looping forever, it will also drop its waking flag soon enough to possibly let another one take it. There used to be a few cases of watchdogs before this on a 24-core AMD EPYC platform on the list iteration those never appeared anymore. The perf has dropped a bit on 3C6T on the EPYC, from 6.61 to 6.0M but remains unchanged at 24C48T.		2024-03-25 17:34:19 +00:00
..
haproxy	OPTIM: ring: have only one thread at a time wake up all readers	2024-03-25 17:34:19 +00:00
import	BUILD: tree-wide: fix a few missing includes in a few files	2024-03-05 11:50:34 +01:00
make	BUILD: makefile: also define cmd_CXX to pretty-print C++ build commands	2024-01-26 18:54:23 +01:00