3 ms·
It sounds like part of the issue is that people think random == evenly (but unpredictably) distributed on a specific (and relatively short) timescale. For a tr
by lazide 3y ago
It sounds like part of the issue is that people think random == evenly (but unpredictably) distributed on a specific (and relatively short) timescale.
For a truly random source, the odds of getting the same number in the next roll are identical to getting it on any prior roll. For example, flipping a coin twice is as likely to get you heads twice as it is to get you heads/tails.
eventually things even out. But if it’s truly random, when that is going to be the case should also be completely unpredictable. It might end up being after the service is deprecated, for instance. You might end up never getting a specific ‘desired’ answer ever. For instance, if the test is flipping a coin and we do it 10 times, there is a small chance we never get tails and get 10 heads in a row from a truly random source.
That is working as expected.
Usually (at least with load balancing) they instead want a smoother distribution, where it’s less likely to get the same answers they just got, when they just got them.
So for example, they’d prefer that if they just got a heads they’re more likely to get a tails next (but it won’t always happen).
Notably, this isn’t really random. It’s also a really hard thing to do in practice without also getting all nodes in lockstep, being predictable to an outside attacker, or having internode communication. Maybe impossible, I don’t remember.