3 ms·
Well, yes, I suppose technically that is correct. In our use case the thread would wake up, check if there was any work to do, if not then sleep(1). If you're d
by gambiting 6y ago
Well, yes, I suppose technically that is correct. In our use case the thread would wake up, check if there was any work to do, if not then sleep(1). If you're doing it continuously(there is nothing to do) the thread would be sleeping for 16ms pretty much exactly every time - which meant that any time any work came in it wouldn't be picked up immediately, but anywhere between 1-16ms(which was unacceptable for this use case).