6 ms·
I'm still waiting for my M1 to show up but from studying the details that other people have commented on, it's clear that Apple is slathering on the microarchit
by jeffbee 6y ago
I'm still waiting for my M1 to show up but from studying the details that other people have commented on, it's clear that Apple is slathering on the microarchitectural resources that both Intel and AMD are stingy with. Their core has a gigantic L1 instruction cache, rather a lot of L1 TLB entries (4x more than Intel), large(r) pages by default, and many other aspects. L1 TLB entries in particular are a well-known problem for x86 performance so it's a real mystery why Intel doesn't simply add more of them. x86 is probably married to 4K pages forever, because of god-damned DOS, whereas Apple can make the default page size be whatever they want it to be. People with high requirements can jump through a million hoops to get their x86 program loaded into hugepages, but on Apple's platform you're getting it for free.
- frogblast 6y agoApple’s core is very wide. But wide usually means very high power consumption. M1 apparently has much lower power consumption. So something else is going on other than “Apple is willing to spend more to make cores wider”.
- BlueTemplar 6y ago> M1 apparently has much lower power consumption. Even compared to similar manufacturing processes ?
- Miraste 6y agoThere are no similar manufacturing processes, Apple has paid for time-limited exclusivity on 5nm.
- tuatoru 6y agoThe manufacturing process is TSMC's, so probably not. To me the innovation is using phone-type SoC technology. A lot of the power (and die area) demand in modern chips is in the interface circuitry to drive the few centimetres of PCB trace between ICs. Put the RAM in the same package as the CPU and you eliminate that interface. That gives you die space and power budget for big buffers and lots of parallel execution. Interface transistors (and wires) are many times larger than the core compute logic transistors (and wires), so there is much more than a one-for-one gain.
- DeRock 6y agoThat, in part, comes from x86 vs arm. x86, with its variable length instructions, means your logic gets increasingly complex as you widen. Meanwhile with arm, you have constant instruction size (other than thumb, but that’s more straightforward than variable size), that lets Apple do things like an 8-bit wide decode block (vs. 4-bit for Intel) and a humongous 630 OOB (almost double Intel’s deepest cores).
- sidewndr46 6y agoFor the uneducated, what is an "OOB" here?
- sounds 6y agoI think that's a typo - the Apple Silicon M1 has a "ROB is in the 630 instruction range" - https://www.anandtech.com/show/16226/apple-silicon-m1-a14-deep-dive/2 https://www.anandtech.com/show/16226/apple-silicon-m1-a14-de... "ROB" and "OOO" might have gotten mixed together here. OOO = Out-of-order. Refers to the fact that the M1 can decode instructions in parallel. ROB = Re-Order Buffer. Refers to the stage where the parallel instructions get put back "in-order" and "retired."
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- jmull 6y agoFrom the Anandtech article[1] on the M1, I think this is referring to the reorder buffer, or ROB. Reorder buffers allow instructions to execute out-of-order, so maybe that's where the "OO" comes from. [1] https://www.anandtech.com/show/16226/apple-silicon-m1-a14-deep-dive https://www.anandtech.com/show/16226/apple-silicon-m1-a14-de...
- DeRock 6y agoYes, I was going by memory, which thought “out of order buffer” was a thing. I meant ROB. Point still stands, in that scaling these blocks is very difficult with variable instruction size.
- andor 6y agoNot a chip designer, but I think it could lead to a more efficient use of the functional units. With more instructions decoded per clock and a larger reorder buffer, the core should be able to keep its units busier, i.e. not wasting energy without producing valuable output. This efficiency gain of course needs to outweigh the consumption of the additional decoders. This part is easier with ARM as decoding x86 is complicated. In addition to higher unit utilization, the increased parallelism should also be an advantage in the "race to sleep" power management strategy.
- raverbashing 6y agoInteresting that you mention page size, IMHO 4k was small even 10 years ago. Though of course the next bump is 4M which I think might be too big for most apps Apparently ARM supports 4KB, 64KB and 1MB (I just googled that) Also maybe all the x86 crud might be finally taking its toll (and not just the ISA but all the cruft that got on top of it for 40yrs+ like legacy buses and functionalities, ACPI, or even the overengineered mess that's UEFI)
- jeffbee 6y agoAll the legacy junk that's actually on the CPU is tiny. Even the x86 instruction decode you could lose in a corner of a 512x512 FMA unit.
- my123 6y ago16KB page size is what arm64 macOS and iOS on Apple A9 onwards use.
- CountSessine 6y agoThere’s nothing wrong with ACPI - in fact it’s what’s going to enable ARM in the server space. Without something like ACPI, you need customized kernels and other crap to control system devices. ACPI is actually quite nice. And it replaced something (APM) that really was legacy cruft (dropping into real mode for power management?!! Ugh!) EFI doesn’t seem that bad either. Maybe something like uboot would suit you better? But the reason we have those nice graphical bios utilities now is because of EFI.
- m4rtink 6y agoWhile Intel is indeed losing the performance game, even with the shady management engine shenanigans intel CPUs are still much more open than the locked down proprietary nightmare that apparently are the new Apple ARM SoCs.
- coward8675309 6y agoThat's why I commute to the office via horse — so I don't need to deal with those fascists at the DMV. Sure the costs of boarding and hay and horseshoes pile up, but at least I'm not being hassled by The Man.
- tjoff 6y agoAnd the PC has been a massive mistake that needs rectifying?
- pjmlp 6y agoFrom the point of view of IBM, most likely yes, otherwise there wouldn't have been PS/2 and MCA architecture. Hence why laptops and 2-1 hybrids are basically back to the days of vertical integration of 16 bit computers, whose the PC was the only exception.
- tjoff 6y agoSo let's all make sure, for apples sake, that is fixed then. Not really, PC laptops and hybrids are pretty standardized. A slim case doesn't really make it vertical integration.
- pjmlp 6y agoTry to use anything other than Windows or ChromeOS on such laptops, with 100% support of underlying hardware.
- 6y ago
- ip26 6y agoIt seems like a straightforward tradeoff of IPC vs scalability. They are able to shovel transistors at the core because there are only 4 of them. AMD on the other hand is packing 64 cores into a package, so each core has to make do with less.
- jeffbee 6y agoI believe my point is that the M1 seems to spend its gate budget where it really helps performance of software in practice, while x86 vendors are spending it somewhere else. AMD in particular wasted an entire generation of Zen by having too few BTB entries. Zen1 performance on real software (i.e. not SPEC) was tragic, similar to Barcelona on a per-clock comparison. They learned this lesson and dramatically increased BTB entries on Zen2 and again for Zen3. But the question in my mind is why would you save a few pennies per million units by shaving off half the BTB entries? Doesn't make sense. They must have been guided by the wrong benchmark software.
- ip26 6y agoI doubt it was about saving their pennies. Zen1 EPYC was a huge package with an expensive assembly & copious silicon area. But it was spread across 32 cores. A larger BTB probably had to come at the expense of something else. What 'real software' are you thinking of? Anything in particular? Just curious, not looking to argue. (sorry I changed my comment around the same time you replied)
- jeffbee 6y agoVery large, branchy programs with very short basic blocks. This describes all the major workloads at Google, according to their paper at https://research.google/pubs/pub48320/ https://research.google/pubs/pub48320/
- yongjik 6y agoIs page size actually a noticeable problem for most people (say, MacBook users)? Linux has supported huge pages for years, and my impression is that it's still considered a niche feature for squeezing out the last percentage of performance. I don't think any popular distro enables it by default.
- dr_zoidberg 6y agoNot just Linux, but windows also has Large Pages support. Back in the day where CPU cryptocurrency mining was still a thing (and for some cryptocurrencies which are aimed towards CPU-mining still is), some mining programs would ask to enable large page support.
- jeffbee 6y agoIf you have a large program putting its text on huge pages can make much more than one percent difference. Any time your program spends on iTLB misses can be eliminated with larger pages.