Intel with all the melt/spec/leak mitigations, the bare-bones syscall cost went from ~70ns to about ~350ns. It's crazy. I think we lost 10 years of system call performance.
-
-
The idea of shared mem protocols is to amortize the cost of syscalls, for example if you have a shared futex then only sometimes you actually have to wait (block) which is a syscall. You go from syscall per unit of work to say ~5 units of work per syscall.
-
oh, so in usual workloads you can frequently send multiple units of work in rapid succession before having to block? that kind of surprises me. but even then, I still think the choice of wakeup primitive and whether you parse data directly from the shared ring are orthogonal.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.