3 ms·
At close to 300 comments, I am surprised there is no mention of what I thought was the most important and surprise, 32 to 70MB L3 Cache. A lot of people focus o
by ksec 7y ago
At close to 300 comments, I am surprised there is no mention of what I thought was the most important and surprise, 32 to 70MB L3 Cache. A lot of people focus on Core and Thread as well as IPC. We already knew what improvement IPC could do, we already knew what we could do 32 Thread. None of these are really new.
But 64MB of L3 Cache? In a consumer CPU at a price that I would hardly call expensive ( I would even go on to call it a bargain ). We used to talk about performance enhancements and cache miss, we now have 64MB to mess with, we could have the whole languages VM living in Cache!
- Manjuuu 7y agoThis, people tend to forget what huge difference a few mb of cache can make. I'd prefer 1Mb more of cache over half a GHz of frequency.
- pedrocr 7y agoThis is a bit pedantic but capitalization matters in units. I think you mean 1MB instead of 1Mb (byte not bit). And "mb" would be a milli-bit or a thousandth of a bit, which is a unit that probably makes sense in some situations (e.g., estimating information content of a message). (There's also the extra complexity around MiB vs MB for base 2 vs base 10 prefixes. In this case it would actually be MiB as RAM and cache is normally base 2 sized. But not everyone uses that, relying on convention from context instead.)
- pedrocr 7y ago>we could have the whole languages VM living in Cache When dual-core processors came out someone said you could now have one core run your stuff and another run the anti-virus. That was widely joked about. This feels a little close to that. Having more CPU cache than we recently had RAM ending up being used for programming language overhead.
- ncmncm 7y agoAgreed. For those of us using VMs, the extra cache in each package is enough for the working set of the systemd we are obligd to run in each VM. Looking back to the 8M total RAM I had on a Mac SE/30, running A/UX Unix and a MacOS GUI comfortably, the sloppiness of modern productions is a disgrace and an embarrassment. What galls is not the wasteful extravagance. It's the failure of imagination that makes such meager, pitiable use of such extravagance. We make, of titanium airframes and turbojet engines, oxcarts.
- ksec 7y agoAgree with both the comment above, but do we really have a solution? It is a trade off between Cross Platform, time to market and development resources. And unlike any other scientific and engineering industry, Software Development doesn't even agree on a few industry standards, instead everything is hyped up every 2 years and something new come around and becomes a new "standard". And we keep wasting resources reinventing the flat tire.
- zepearl 7y agoThanks for the heads-up - I totally missed this "detail" when I skimmed through the article & specs table earlier today. And just in case that somebody missed it, here is again the link to the PDF "What Every Programmer Should Know About Memory" by Ulrich Drepper... https://people.freebsd.org/~lstewart/articles/cpumemory.pdf https://people.freebsd.org/~lstewart/articles/cpumemory.pdf ...which was posted here sometimes earlier this year and which talks about every detail of RAM and L1/2/3 cache access times and architectures etc... . Very heavy for me (read so far 25%) but as well very interesting.
- dr_zoidberg 7y agoThis! I usually run code where I'm cache limited and adding more processes/threads slows down everything! At 64 MB of L3 cache, I'd be able to run things way faster[0] on image processing tasks! [0] for the curious reader, I've two machines: a 3MB-L3 i5 and a 20MB-L3 Xeon. So id't be looking at 20x and 3x improvements -- without taking into account other architectural improvemnents, like not-underclocked-AVX2, and the GHz count