ipc-bench VS multichase

Anyone who thinks they understand unix signals is fooling themselves. Anyway, the basis of the claim that you can exchange half a million small messages per second using signals is misunderstanding. The benchmark suite in question passes no data, it only ping-pongs the signal.

https://github.com/goldsborough/ipc-bench

Having now done some benchmarking, I would like to use shared_memory.

I only use AF_UNIX sockets when I need to pass open file handles between processes. I generally prefer message queues: https://linux.die.net/man/7/mq_overview

I haven’t measured myself, but other people did, and they found the latency of message queues is substantially lower: https://github.com/goldsborough/ipc-bench

After reading your post, it seems as if you are interested in something called Inter Process Communication (IPC). There are as many solutions to this as there are birds in the sky (not really, but almost). If you want _speed_, take a look at this benchmark comparison: https://github.com/goldsborough/ipc-bench.

I have some experience writing/modifying linked-list benchmarks (https://github.com/google/multichase) specifically to test memory latency.

It is extremely difficult, maybe impossible, to design a prefetcher that can predict the next cacheline(s) to prefetch in a linked-list. I am not aware of a single CPU that can do this consistently.