notexOPENOverview
Notex/Systems/Latency numbers every programmer should know
02.03LESSON 03 OF 6 · 1 MIN READ

Latency numbers every programmer should know

Always free to read
SECTION VIDEOLatency numbers every programmer should know

Video coming soon. Start with the reading below.

COMING SOON

Dr. Dean from Google reveals the length of typical computer operations in 2010 [1]. Some numbers are outdated as computers become faster and more powerful. However, those numbers should still be able to give us an idea of the fastness and slowness of different computer operations.

Back-of-the-envelope estimation — original diagram 27

Notes ----------ns = nanosecond, μs = microsecond, ms = millisecond 1 ns = 10^-9 seconds 1 μs= 10^-6 seconds = 1,000 ns 1 ms = 10^-3 seconds = 1,000 μs = 1,000,000 ns

A Google software engineer built a tool to visualize Dr. Dean’s numbers. The tool also takes the time factor into consideration. Figures 2-1 shows the visualized latency numbers as of 2020 (source of figures: reference material [3]).

Back-of-the-envelope estimation — original diagram 28

By analyzing the numbers in Figure 2-1, we get the following conclusions:

  • Memory is fast but the disk is slow.
  • Avoid disk seeks if possible.
  • Simple compression algorithms are fast.
  • Compress data before sending it over the internet if possible.
  • Data centers are usually in different regions, and it takes time to send data between them.
Progress is saved on this device.
KEEP EXPLORING

One note leads to another.

Back to the library →
⌕
Search across the entire library ⌘ K