jitter

To the extent that my model predicts jitter better than random, an entropy source derived from CPU jitter is weaker.

Indeed, they may actually reduce jitter if you're careful ( they should not but that's another story ).

Of course, stuff like indirect branches and self-modifying code can really throw a wrench in your JITter's gears.

In the end, this increases the likelihood that the OS reschedules the application thread, which becomes visible as jitter.

This glosses over the fact that your service even can geo-scale well over high latency and high jitter networks.

A little too much motion going on in the background with just enough jitter to give me a headache.

It might be better if it could be made buttery smooth or perhaps slower scrolling to try and reduce the jitter?

There are several entropy sources like this -Havege, jytter and Dakarand all tries to use jitter and unpredictable behavior in CPUs.

TCP never sees enough data to construct a good bandwidth/delay/jitter model of the channel.

You may not realize it but jitter, latency, routing, etc are far, far better on proper business lines.

This complements well with their architecture,which basically allows real-time without jitter, and with very high accuracy/speed, through usage of multiple virtual cores.

Also the jitter between electrical and optical synchronization is in the order of few ps, which is important for things like Doppler-OCT.

The problem with backtesting low latency (by which I mean switch-to-switch roundtrips of < ~ 50us) is there are so many sources of jitter the data is basically "mean of x, st dev of 6x^3".