look at the PPA not peaks you are comparing a 1.1mm2 core vs 3. something mm2 coreIf that's the best x86 can do, then I think the logical conclusion would be that x86 is fundamentally worse than ARM.
look at the PPA not peaks you are comparing a 1.1mm2 core vs 3. something mm2 coreIf that's the best x86 can do, then I think the logical conclusion would be that x86 is fundamentally worse than ARM.
Skymont is great for what it is (definitely better PPA than Lion Cove), but it's still behind the Apple P-cores and Oryon. Geekerwan's video on the 8 Elite compares Skymont to the M3 P-core directly and it has Oryon V2 in another chart.look at the PPA not peaks you are comparing a 1.1mm2 core vs 3. something mm2 core
like i said take core sizes and caches into consideration ~3X the core size btw for M3PSkymont is great for what it is (definitely better PPA than Lion Cove), but it's still behind the Apple P-cores and Oryon. Geekerwan's video on the 8 Elite compares Skymont to the M3 P-core directly and it has Oryon V2 in another chart.
Ampere and Fujitsu cores never targeted these markets.Every ARM core was designed to target smartphone and laptop.
If you look at the full context of my comment I said:Ampere and Fujitsu cores never targeted these markets.
ARM CPUs on the market today
I'm more so looking for technical reasons.
The front-end for an x86 CPU is going to be a lot more complex just because of the ISA itself. An ARM CPU (in general as there are some exceptions) just needs to deal with a smaller number of 32-bit instructions. With x86 you've got hundreds of instructions ranging in length from 8 bits all the way up to 120 bits.
Having to deal with that requires more transistors and there's not much that can be done to get around that.
I'm inclined to agree with this. But maybe we should look at the cumulative R&D spend. I'm not sure how reliable this data is but we have such a graph:The main reason Apple/Qualcomm are beating Intel/AMD is they have more money.
1t perf/w is still quite a bit better on SDXE iirc, it's just that it has not much else going its way. (also you need a unicorn in 80/84100)I'm inclined to agree with this. But maybe we should look at the cumulative R&D spend. I'm not sure how reliable this data is but we have such a graph:
Stock Comparison Tool | MacroTrends
www.macrotrends.net
I presume as portion of spending AMD likely has the highest percentage of their total spend on CPU development. But since they're also the smallest total spend, especially cumulatively, does the graph suggest that they will be catching up to Qualcomm? (Though, in my personal weighing they're also already ahead e.g. HX370 vs. X1E)
Indeed. But I noted my personal preference for a reason. I do not wank to efficiency charts. The reason I like M1 and M4 is because they avoid fan noise while browsing even bloated websites. And the X1E-80 Samsung I tried also failed that test and so, in my estimation, it is effectively equal to the HX370 in the "real world benefit" to this category and behind due to all its other defeats.1t perf/w is still quite a bit better on SDXE iirc, it's just that it has not much else going its way. (also you need a unicorn in 80/84100)
I'm inclined to agree with this. But maybe we should look at the cumulative R&D spend. I'm not sure how reliable this data is but we have such a graph:
Stock Comparison Tool | MacroTrends
www.macrotrends.net
So question: is ARM architecture created from the ground up to minimize resource idling hence SMT isn't necessary?Exactly this. Once super scaler designs hit the market, there were all these execution engines just sitting around most of the time waiting for those moments of maximum parallelable instructions to come along and use them.
For the other 90% of the time they would be left unused.
SMT took care of this by using them when they weren't being used.
No. The fundamental issue is that single core perf got hard to scale and multicore was a lot easier so we went that route. But a lot of problems can't be multithreaded, like at all. Because a lot of server work is a lot of parallel jobs, more slower cores may be a better trade than fewer faster ones, depending on how sensitive you are to how quickly each job gets done. For instance web servers don't really need a lot of single thread perf. Each request can get it's own thread so is parallellizes nicely, and you tend to be bottlenecked behind database access so CPUs tend to be a bit idle. HPC usually goes the other way - there's a cost to threading it so fewer/faster threads are better. Basic desktop tasks tends to be more single core oriented, depending on what you're doing, but with the benefit that you might have a lot of disparate processes all going on you can spread across those cores.So question: is ARM architecture created from the ground up to minimize resource idling hence SMT isn't necessary?
Er, yes and no. I don't think the performance of the M4 is a product of money. I think it's a product of much better design decisions, owing more to them not having to fit Apple Silicon to a diverse set of customers all with different needs. It's extremely tailored. I think in terms of their ability to put one of the highest volume architectures on the leading node, that's money. What would M4 look like if it was still on 5nm? Not as good. But on the same process AS seems to still beat Intel/AMD on single core, perf/watt, etc.The main reason Apple/Qualcomm are beating Intel/AMD is they have more money. Same reason Intel beat the RISC vendors a generation ago. Maybe someday something comes along which is a bigger consumer market than smartphones and ARM/Apple/Qualcomm are displaced in favor of something else for the same financial reasons.
No, a better answer would be what x86 would look like if it wasn't saddled with an unbundled market that requires those tradeoffs. It's not like they're either a technological or economic limitation - just a business choice, and therefore arbitrary.A better answer would be what would M4 look like if it had to make the tradeoffs Intel/AMD make
ARM CPUs on the market today
If we're being pedantic, ARM Neoverse is still derived from ARM's X3 smartphone cores. Whether that qualifies as designed for smartphones vs designed for servers is not straightforward to answer in my opinion. Though I don't particularly care either way. What's your point? I don't think that detracts from my overall point that ARM cores target lower power use-cases than x86 cores.![]()
Ampere® Altra® Arm-based Workstation
Specification may change without notice. Product may differ from images shown. Single Ampere® Altra® or Ampere® Altra Max Processor RAM: 8 DIMMS, 1DPC, 2933/3200MHz, ECC, max 2048GB. Storage: 2x M.2 NVMe PCIe x4 SSD 2280. Storage option: up to 8x SAS/SATA SSD/HDD, RAID option, from add-on...store.avantek.co.uk
I think ARM was created to solve some problems that x86 was very poorly architected to solveSo question: is ARM architecture created from the ground up to minimize resource idling hence SMT isn't necessary?
I think we need to be a bit clearer on what we mean here. x86 exists to serve one, potentially two markets - consumer PCs/servers. That's it. It's garbage for everything else.I think ARM was created to solve some problems that x86 was very poorly architected to solve.
Good points and this is exactly why comparing x86 to Apple Silicon is a fool's errand. It's like comparing public transportation to private transportation. The fact that x86 is as good as it is (thanks mostly to AMD) is a miracle.Those are all the same ISA. They are mostly the same core design philosophy until you get to Apple's work where it peels off into this whole space that x86 can't even enter because they get a 'greater than sum of its parts' benefit by co-designing against Swift and LLVM and in-house asymmetric cores and memory architectures and bespoke schedulers and a zillion other things that Intel/AMD often have zero control over. So the question of 'what was ARM created to solve' is very, very different from 'what was Apple Silicon created to solve'.
Apple Silicon was created to maximize the benefits of all of the other technologies Apple controls for the benefit of device performance that no OEM can possibly match because nobody has control of the stack. Apple gets to shove compute out of the P core and onto AMX or onto ANE because they write the APIs, they write the support libraries, they write the compiler, they design the language and they get to decide from this enormous tool shop which set of tools to employ to solve a given problem. They don't need to rely on SMT. x86 has a lot less latitude there.