5 ms·
I would be interested in a computer science only version. A quick search didn't bring up an already existing one :(
by egnehots 2y ago
I would be interested in a computer science only version.
A quick search didn't bring up an already existing one :(
- Sajarin 2y agoIsn't the computer science version Peter Novig's, "Latency Numbers Every Programmer Should Know" table? https://norvig.com/21-days.html#answers https://norvig.com/21-days.html#answers Edit: This version is also quite nice - https://gist.github.com/hellerbarde/2843375 https://gist.github.com/hellerbarde/2843375
- teraflop 2y agoOne classic set of numbers is Jeff Dean's "latency numbers every programmer should know", as quoted in a bunch of places including: https://highscalability.com/google-pro-tip-use-back-of-the-envelope-calculations-to-choo/ https://highscalability.com/google-pro-tip-use-back-of-the-e... (EDIT: apparently Dean got this table from Peter Norvig as another commenter mentioned.) The disk numbers are a bit outdated now because of the overwhelming shift from spinning hard disks to SSDs, but most of the others have held up surprisingly well AFAIK. For instance, neither CPU L1 caches nor the speed of light have gotten dramatically faster in the last couple decades.
- shepherdjerred 2y agohttps://github.com/sirupsen/napkin-math https://github.com/sirupsen/napkin-math