Latency Numbers, visualised and memorised

Previous Post
The inherent Asymmetry of online attacks
Next Post
So what is the state of the Ads mess?
There is a well known Github Gist “Latency Numbers Every Programmer Should Know ”, which explains which things take how long.
If you scale these things down 3 billion times, a clock cycle (0.3ns) becomes a second. And suddenly things are relateable. (Tweet )
Another attempt to visualize this , not entirely unlike this XKCD .
Previous Post
The inherent Asymmetry of online attacks
Next Post
So what is the state of the Ads mess?