HN Hall of Fame Weekly email

What every programmer should know about memory, Part 1 (2007)

Screenshot of lwn.net captured 2026-07-20
Page preview · captured 2026-07-20

Resurfaced independently across 9 calendar years, with breakout response in 3 of them.

submissions
10
submitters
10
observed span
2007–2025
peak thread · 53 comments
129 pts
latest 20+ return · 2021-01-25
123 pts

Submission timeline

2007–2026

One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.

First comments on top threads

HN comment order

Does every programmer really need to know the physics behind dynamic ram? What every programmer should know is the latency of the various memory types (cache, RAM, virtual) and their respective sizes. Here's a nice graphic: http://duartes.org/gustavo/blog/post/what-your-computer-does...

A few observations about what's changed since this was written: The layout shown in Figure 2.1 with a traditional shared Front Side Bus linking CPUs to the northbridge is a long-dead design, having been retired from mainstream products by AMD around 2003 and by Intel around 2008. Since then, the northbridge and memory controllers have been on the CPU die(s) for almost all products. AMD's Zen 2 and later desktop/server CPUs split the northbridge back out to a separate die…

wtallis·123-point thread·

https://hn.algolia.com/?query=What%20every%20programmer%20sh...

dang·119-point thread·

The entire article is also available at: http://people.redhat.com/drepper/cpumemory.pdf

btn·117-point thread·

The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.

Breakout years
3

100+ points or 50+ comments

Total points
604

reference only — not used in Hall rules or ranking

Total comments
133

reference only — not used in Hall rules or ranking

Every submission