3 ms·
>The article even mentions an arguably better approach (check on a timer), but for some reasons claims it is worse. How do you know what timeout to use for the
by meindnoch 1y ago
>The article even mentions an arguably better approach (check on a timer), but for some reasons claims it is worse.
How do you know what timeout to use for the timer? You may end up with tons of unnecessary polling if your timeout is too short, or high latency if your timeout is too long.
>Standard C++ has one albeit somewhat overcomplicated, senders and receivers
*in C++26
- pjmlp 1y agoOr CUDA, which is getting its own compute version.
- mgaunard 1y ago> how do you know what timeout to use? adjust based on your minimum expected latency, potentially with exponential backoff. Potentially account for scheduler overhead of the spurious wake-ups. Basically if you check every millisecond to every 10ms, you should be fine. > in C++26 it's a library, language support is not necessary. There are implementations you can use right now.