3 ms·
> and where delays aren't super costly This is key. If delays aren't costly, sure, any algorithm is fine. But if you want your service up as soon as possible
by jstanley 2y ago
> and where delays aren't super costly
This is key.
If delays aren't costly, sure, any algorithm is fine.
But if you want your service up as soon as possible, why spend pointless minutes calling sleep() when you could be getting things working sooner?
- dragonwriter 2y ago> If delays aren't costly, sure, any algorithm is fine. Not true, delays aren't the only costs. Compute, network, and developer time digging through logs all cost money, and hammering a service fruitlessly when it is down adds to all of those. (It also doesn't help that “system is overloaded” may sometimes be communicated clearly, but also in many systems can manifest in... just about any other kind of error, too.)