By the way, talking about memory solutions, here is a little patent someone linked on RWT:
Multi-CPU, in this case SoCs, would make it extremely complicated for the OS and applications to full utilize. The reason why servers have multiple CPUs is that cloud companies sell resources by the core and each core can be used by different customers at the same time.In terms of economies of scale & supply chain would it make any sense to make specialized chips specifically for mid-range to high-end Macs that probably sells less than 4.5 million units per year?
Would it not make more sense to have multiple M1 SoCs instead in 1 Mac? In terms of logic board space Macs have plenty compared to say a iPad Pro.
TIL that MP servers didn't exist until "cloud companies" ? ?The reason why servers have multiple CPUs is that cloud companies sell resources by the core and each core can be used by different customers at the same time.
I didn't say that.TIL that MP servers didn't exist until "cloud companies" ? ?
I didn't say that.
The reason why servers have multiple CPUs is that cloud companies sell resources by the core and each core can be used by different customers at the same time.
this, indeed can be called...M2 since the M1x is reserved for the upcoming Macbook Air
The A15 will use M2 cores, not vice versa.I presume "M2" will use the A15 as it's base, just as "M1" used A14.
There is a chance of consumer confusion if a 2023 MacBook Air is on M3 and a 2023 MacBook Pro is on M2X, but to be honest I think Apple can handle that via marketing and product positioning and those who are performance-focused will already be looking at the CPU+GPU core counts and benchmarks so they will know going in the M2X is faster than the M3 on most/all tasks.
I mean the iPad Pro being on an A12X/A12Z with the iPhone on A13 and A14 didn't really confuse people about how much more powerful the iPad Pro was over the iPhone. Even the iPad Air on A15 was still lapped in a some performance areas by the iPad Pro on A12Z thanks to the additional CPU and GPU cores.
The A15 will use M2 cores, not vice versa.
...which they will…Well it's a "which came first: the chicken or the egg?" question since we assume both the M2 and A15 will use the same next-generation performance ("Avalanche") and efficiency cores. So if the 14/16 MBP launch next month at WWDC with M2...
What's that mean? I thought the way people were using M2 vs. M1x is the number referred to the generation, and the letter referred to the "series". Thus an M2 would be the next-gen low end chip, and the M1x would be the first-gen midrange chip. Given this, wouldn't the 10-core chip be an M1x and not an M2?I continue to stand by my (not at all informed by any wine I swear) claim that these will be M2 and not M1x.
The definition according to cmaier is that an M2 would use an updated architecture, whereas an M1whatever would use the base architecture of the A14 or M1 but configured differently (more cores, larger LLC, LPDDR5 memory controller et cetera).What's that mean?
What's that mean? I thought the way people were using M2 vs. M1x is the number referred to the generation, and the letter referred to the "series". Thus an M2 would be the next-gen low end chip, and the M1x would be the first-gen midrange chip. Given this, wouldn't the 10-core chip be an M1x and not an M2?
Wait wait wait.I have the feeling that many people are getting too carried away with hypothetical chip names and completely loose the sight of what actually matters.
Based on ARMv9? ?Apple Silicon Arch Next ----> A15
|
----> Apple Silicon Desktop
Are you seriously trying to tell me MR members are getting all worked up focussing on aspects that are completely unrelated to the functionality, because of some preconception they have about it?
Based on ARMv9? ?
Truly. If they're reworked so much that we only need 2 of them here, then why would the report claim we're still getting 4 on the M1 successor and even 8 on whatever will go in the Mac Pro? It's really bizarre.The 8+2 core configuration is weird
Truly. If they're reworked so much that we only need 2 of them here, then why would the report claim we're still getting 4 on the M1 successor and even 8 on whatever will go in the Mac Pro? It's really bizarre.
I have the feeling that many people are getting too carried away with hypothetical chip names and completely loose the sight of what actually matters. As you aptly pointed out, what we should care about is whether the alleged prosumer 10-core (or whatever) chip is going to be based on the same architecture as A14 and M1, or is it going to be based on their successor. It would probably be helpful to have some sort of way to refer to the architecture itself somehow. We know internal names for the GPUs (the A14/M1 GPU is G13 for example), but I am not aware of any codenames for the CPU architecture.
Finger's off my M1Z Pro Tagmemics Fusion Advanced Plus!
According to Mark Gurman:
For the new MacBook Pros, Apple is planning two different chips, codenamed Jade C-Chop and Jade C-Die: both include eight high-performance cores and two energy-efficient cores for a total of 10, but will be offered in either 16 or 32 graphics core variations.
Are these the codenames for the SOCs or the CPUs?
I read this article recently, which shows that Apple is using the efficiency/performance cores differently based on the QoS of the process. I think that it's pure genius (because it actually prioritizes task, not only relative to other tasks, but also to save battery and avoid slowing the system). And it's further proof that Apple likely won't ship pro chips (whatever they call them) with less efficiency cores than the consumer version, as all processes with utility/background QoS run on efficiency cores only. If anything, I would expect them to have more, maybe even proportionally.- The 8+2 core configuration is weird, as Icestorm cores are very small already and it doesn't sound like dropping two of them makes much sense, if any. This suggests that the efficiency cores in the alleged 10-core chip will see a significant rework.
I read this article recently, which shows that Apple is using the efficiency/performance cores differently based on the QoS of the process. I think that it's pure genius (because it actually prioritizes task, not only relative to other tasks, but also to save battery and avoid slowing the system).