Not a concurrency professional, but my first impression is whether to yield or
spin depends on how costly the task you are waiting is - I know yield involves
a context switch and can be problematic for small waits.
In addition, in Java, many blocking happens in a way users cannot control - for
Seems you misunderstood my question. It was *not* what is best to do. It
was: "Does the core-libs team have a common-sense / best practice for
busy-wait.". The latter is a clear and concise question, and the answer
could be as simple as "yes" or "no".
Am 15.06.2025 um 18:40 schrieb Archie Cobb
Just MHO...
This is kind of like asking "What's the best way to waste electricity?"
It's a nebulous question until you specify what "best" means in this odd
scenario
-Archie
On Sun, Jun 15, 2025 at 11:09 AM Markus KARG wrote:
> Recently I was asked by a programmer, what to do if there sim
Recently I was asked by a programmer, what to do if there simply is no
other way than actually busy-wait.
I see several options:
* Do nothing: Costs valuable CPU time and increases carbon footprint.
* Do a power-nap: Thread.sleep(1)
* Be fair: Thread.yield() gives other threads a chance to ex
