What Every Programmer Should Know About Memory (2007) [pdf]

people.freebsd.org

102 points·gszr··15 comments

This is an incredibly useful guide, but it starts out with transistor level stuff that I at least find much less relevant.

The good stuff starts at section 3, CPU Caches.

I found it insightful as it makes you realize the following important takeaway: we can still improve bandwidth, but not latency.

this is a good article, I remember it from a while back. Does anyone know what the rule is on duplicates? How do some come through? I always just get redirected to a reference for the old posting.

Some content is evergreen. The software May account for that. With linked documents, the URI may be different as well.

The last meaningful discussion was about three years ago. The first was close to seven. The HN community has grown since both those times, but still deals with CPU memory.

> Does anyone know what the rule is on duplicates?

https://news.ycombinator.com/newsfaq.html

thank you, just finished reading the FAQ - also discovered how a poll is made in the process - I always thought that was just a karma level thing :)

Duplicate...

https://news.ycombinator.com/item?id=58627

https://news.ycombinator.com/item?id=3919429

https://news.ycombinator.com/item?id=8216215

Last time posted was almost a year ago, the information is still very much relevent and interesting.

It is almost 8 years ago. Do we anything new to learn in this area?

Probably, if you started studying or learning software engineering sometime between then and now.

"Get off my lawn!"

What's the point of comments like this?

There were so few comments in this thread I ended up reading through the comments in the other ones. One of those links is far more rich in discussion.

Presumably this one: https://news.ycombinator.com/item?id=3919429

Reply on news.ycombinator.com