News for hackers. Stuff that matters.
Re:Latency numbers every programmer should know (2012) by tayo42 on Saturday October 08, 2016 @05:27PM (#12668808)
I came across this article the other day for the first time and started to read it. How much still applies to today?
Re:Latency numbers every programmer should know (2012) by Const-me on Saturday October 08, 2016 @08:01PM (#12669283)
Part 1: 50% applies, RAM controllers now part of the CPU, deprecating half of what’s written, also some CPUs have eDRAM. Part 2: almost completely applies. Part 3: 70% applies, hardware SLAT (Intel EPT / AMD RVI) deprecated what’s written about virtualization. Part 5: 90% applies. The rest of them — don’t know.

P.S. What’s I dislike most about the article, it fails to explain why L3 cache is 10-20 times slower than L1 cache, while they both made from SRAM.

Re:Latency numbers every programmer should know (2012) by nateberkopec on Saturday October 08, 2016 @08:28PM (#12669331)
> it fails to explain why L3 cache is 10-20 times slower than L1 cache, while they both made from SRAM.

Why is it? Is it because L3 is usually shared?

Re:Latency numbers every programmer should know (2012) by Const-me on Saturday October 08, 2016 @08:38PM (#12669355)
Even when the cache line is unshared, L3 is still 10 times slower than L1.

The best explanation I saw is this: https://fgiesen.wordpress.com/2016/08/07/why-do-cpus-have-mu...

Re:Latency numbers every programmer should know (2012) by bogomipz on Saturday October 08, 2016 @08:45PM (#12669368)
I think generally the larger the cache the higher the latency. I think various factor are things like available power budget, some increase in signal propagation delay and more complicated logic needed in a larger search space.
Re:Latency numbers every programmer should know (2012) by Alphasite_ on Saturday October 08, 2016 @08:56PM (#12669383)
Without having read the article I assume it is something to do with the asseociscativity and size of it?
Re:Latency numbers every programmer should know (2012) by alcari on Saturday October 08, 2016 @06:37PM (#12669035)
From a quick look through, most of it. Modern x86 micro-architectures still use integrated memory controllers and ~3 level CPU caches.

All the timings are a little faster, the caches a little bigger, and the buses a little wider, but it's still basically the same stuff with different names.

Re:Latency numbers every programmer should know (2012) by bogomipz on Saturday October 08, 2016 @09:14PM (#12669434)
I think its less important to know the exact numbers since those are a moving target but its more important to understand the orders of magnitude in difference from fastest to slowest and in between.
Re:Latency numbers every programmer should know (2012) by a3n on Saturday October 08, 2016 @06:14PM (#12668962)
Things haven't changed much since the other day, so probably all of it.
Re:Latency numbers every programmer should know (2012) by cornstalks on Saturday October 08, 2016 @06:20PM (#12668982)
GP probably didn't mean "9 years ago" (the article was published over 9 years ago) when saying "the other day." 9 years is a long time in the tech world. It's a valid question.
Re:Latency numbers every programmer should know (2012) by honkhonkpants on Saturday October 08, 2016 @07:29PM (#12669216)
Why do you say so? AMD k8 came out 14 years ago and PC architecture is basically unchanged since.