Why use RAII in lock-free programming?! That seems like completely unnecessary overhead when you're trying to squeeze out performance. Instead you should malloc a huge page at startup and manage it yourself in an arena/pool or a circular buffer.
i like my GIL actually everything that needs to be fast can be outsourced ... which brings me here but the fewer times that i have to actually do complex and cool work, the fewer bugs i can produce
Kinda sad that he spends nearly an hour explaining this technique and concludes with "you should only use this as a last resort, and even then it might not help".
![Lock-free programming with modern C++ - Timur Doumler [ACCU 2017]](/img/n.gif)
Great talk! The GOTO killed me at 16:00 but it make total sense, like you said in lock-free world forget everything you know 😀
This was great. Thanks for sharing.
Great talk!
Btw, there is a typo on the "push" slide. It says "count.compare_exchange". I believe it should be "stack.head.compare_exchange", right?
Yes, I suspect you are right.
how can I get the slides?
Why use RAII in lock-free programming?! That seems like completely unnecessary overhead when you're trying to squeeze out performance. Instead you should malloc a huge page at startup and manage it yourself in an arena/pool or a circular buffer.
i like my GIL actually
everything that needs to be fast can be outsourced ... which brings me here
but the fewer times that i have to actually do complex and cool work, the fewer bugs i can produce
Kinda sad that he spends nearly an hour explaining this technique and concludes with "you should only use this as a last resort, and even then it might not help".
This was the conclusion on every talk i ever saw. Don't go lock free, just use locks 😂
rofl - thats was super funny @ 36:00 ish