Skip to content

Instantly share code, notes, and snippets.

@hellerbarde
Forked from jboner/latency.txt
Created May 31, 2012 13:16
Show Gist options
  • Select an option

  • Save hellerbarde/2843375 to your computer and use it in GitHub Desktop.

Select an option

Save hellerbarde/2843375 to your computer and use it in GitHub Desktop.
Latency numbers every programmer should know

Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns             
Compress 1K bytes with Zippy ............. 3,000 ns  =   3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns  =  20 µs
SSD random read ........................ 150,000 ns  = 150 µs
Read 1 MB sequentially from memory ..... 250,000 ns  = 250 µs
Round trip within same datacenter ...... 500,000 ns  = 0.5 ms
Read 1 MB sequentially from SSD* ..... 1,000,000 ns  =   1 ms
Disk seek ........................... 10,000,000 ns  =  10 ms
Read 1 MB sequentially from disk .... 20,000,000 ns  =  20 ms
Send packet CA->Netherlands->CA .... 150,000,000 ns  = 150 ms

Assuming ~1GB/sec SSD

Visual representation of latencies

Visual chart provided by ayshen

Data by Jeff Dean

Originally by Peter Norvig

Lets multiply all these durations by a billion:

Magnitudes:

Minute:

L1 cache reference                  0.5 s         One heart beat (0.5 s)
Branch mispredict                   5 s           Yawn
L2 cache reference                  7 s           Long yawn
Mutex lock/unlock                   25 s          Making a coffee

Hour:

Main memory reference               100 s         Brushing your teeth
Compress 1K bytes with Zippy        50 min        One episode of a TV show (including ad breaks)

Day:

Send 2K bytes over 1 Gbps network   5.5 hr        From lunch to end of work day

Week

SSD random read                     1.7 days      A normal weekend
Read 1 MB sequentially from memory  2.9 days      A long weekend
Round trip within same datacenter   5.8 days      A medium vacation
Read 1 MB sequentially from SSD    11.6 days      Waiting for almost 2 weeks for a delivery

Year

Disk seek                           16.5 weeks    A semester in university
Read 1 MB sequentially from disk    7.8 months    Almost producing a new human being
The above 2 together                1 year

Decade

Send packet CA->Netherlands->CA     4.8 years     Average time it takes to complete a bachelor's degree
@MartyGentillon

Copy link
Copy Markdown

@Kevin-Hamilton There is a reason to stretch it out that much. From a human perspective, it is really hard to do anything in less than a second. As such, the ridiculously long times give you a better idea of what a computer might be able to do during that disk seek, if it weren't waiting for that disk seek.

Because of this, most of the similar pages I have seen use something like 1 second for a clock cycle (so multiply everything there by 3 or 4). It gives a really good sense of machine sympathy.

@mpron

mpron commented Oct 12, 2016

Copy link
Copy Markdown

Last year, I came up with this concept for an infographic illustrating these latency numbers with time analogies (if 1 CPU cycle = 1 second). Here was the result (attached, and here's a link: http://imgur.com/8LIwV4C)pic

@cth027

cth027 commented Nov 19, 2016

Copy link
Copy Markdown

Excellent idea ! Great page !
Perhaps an interesting comparison:

@MAZHARMIK

Copy link
Copy Markdown

Cool. Loved it.

@hhimanshu

Copy link
Copy Markdown

very interesting!

@imonti

imonti commented Mar 31, 2017

Copy link
Copy Markdown

Excelent Gist.

@LeonZhu1981

Copy link
Copy Markdown

great!!!

@YLD10

YLD10 commented Jul 9, 2019

Copy link
Copy Markdown

Thanks ^o^

@vinaypuranik

Copy link
Copy Markdown

Awesome gist! Thanks

@xenowits

Copy link
Copy Markdown

wowww!!

@vapniks

vapniks commented Nov 14, 2019

Copy link
Copy Markdown

@jiteshk23

Copy link
Copy Markdown

These numbers seem old. This page is updated : https://people.eecs.berkeley.edu/~rcs/research/interactive_latency.html

@Code2Life

Copy link
Copy Markdown

cool!

@eduard93

eduard93 commented Jan 3, 2022

Copy link
Copy Markdown

What about register access timings?

@hellerbarde

hellerbarde commented Jan 6, 2022

Copy link
Copy Markdown
Author

@eduard93 I think register access happens within one CPU cycle. Which, at 2.4 GHz would be 0.417 nanoseconds, which is very similar to the L1 cache reference. I'm not sure if that's true, because I'm not incredibly familiar with modern CPUs. Feel free to fact check this.

@Yougigun

Yougigun commented Nov 7, 2022

Copy link
Copy Markdown

thasnk

@zhangchiisgy

Copy link
Copy Markdown

nice

@sitansu04

Copy link
Copy Markdown

thats cool!

@weizhiwen

Copy link
Copy Markdown

cool!

@Shivam5022

Copy link
Copy Markdown

thanks for this, loved it

@KimJin788

Copy link
Copy Markdown

Cool

The human reaction time:
Average Reaction Times

  • Visual stimulus: 150-300ms
  • Audio stimulus: 140-160ms
  • Touch stimulus: 130-150ms

@popatrader

Copy link
Copy Markdown

Here's a nanosecond: https://www.youtube.com/watch?v=9eyFDBPk4Yw

That's really amazing way to see

@C-Jeril

C-Jeril commented Nov 9, 2025

Copy link
Copy Markdown

You might find some reaction games here: https://kuakua.app/games/reaction-speed

@Wilhelm-Lee

Copy link
Copy Markdown

amazing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment