Pretty good chance Apple is going to point at GPU cores for those who have massive embarrasingly parallel compute needs. ..
Honestly, if Apple does this, I think it'll be the dual GPU issue all over again. Them trying to skate to a puck they think exists, but then doesn't materialize.
That is is where the puck has already gone in vast majority of "embarrasingly parallel" workloads. If go the the TOP500 supercomputer list and yank the GPU cards from all of those systems, the large majority of those systems drop out of the TOP 500 list.
don't need to get to Dual GPUs to get to one or two order of magnitude more cores in a GPU than CPU. Even more so for graphics oriented problems where the result is going to displayed anyway when done with the computation. There have been hundreds of posts in this Mac Pro forum about how Apple is doomed if they don't have CUDA . that isn't just Apple pointing at GPUs for a large share of the compute that is customers. To imply this is some future thing that nobody is doing right now was dubious back in 2013 when Apple rolled out the dual GPU system. At this point though this point it is just disconnected from relatively. Heavy parallel compute has moved over to GPUs in a extremely significant way. Nothing about " guessing where puck is going" at all.
If Apple doesn't provision the ability for multiple discrete GPUs in the next Mac Pro then it will fail horribly. Period.
So Apple pointing at discrete GPUs for "embarrassingly parallel" computation work will be the same thing most of the customers are doing also.
In terms of performance per watt efficiency GPUs generally beat CPU cores. Those cores are usually smaller and more focused just computing rather than branching and non compute tasks.
Especially when Apple also has to push the boulder up the hill with Metal for compute.
If it is Metal vs CUDA then Apple has more than enough money and patience to push that boulder up the hill.
The not so encouraging sign is that Apple hasn't turned the corner on taking OpenCL off the deprecated list. If OpenCL stars getting more adoption traction again and Apple bails they'll have problems.
But isn't just Metal. If Apple wraps the acceleration libraries around some chosen 3rd party GPUs ( AMD and Intel) then . Alot of the 'noise" about CUDA is about libraries of code, not super custom code. Metal isn't behind as much as the libraries are behind.
All the more reason Apple is better off giving us some idea what the end goal of an "8,1" is in advance, IMO.
You are looking for ham from a strict orthodox Jewish kosher store. You can have an opinion that they should serve ham but they don't believe in it. It isn't mainly about the product.
Apple isn't going to talk extensively about a product is probably two years out. ( Or maybe one year out and the "end of the line" for Mac Pro over the long term. if sales are so bad they don't really want to do it very long term anymore. Release a 8,1 with Sapphire ridge next year and except from the "transition" because end of the line. I don't think that is a likely path though. I think Mac Pro is coming at the end with whatever they come up with and they'll just "sleep" on the Mac Pro for 3 years. That's fits the pattern on the iMac Pro and MP 2013. )
That's my whole point though. It's not a good look.
If stand on your head and look at it funny perhaps. but Apple handing over the old "design mule" boxes they have been using for the past 1 (probably closer to 2 ) years to outside developers is pretty indicative that they have other , even newer boxes for their own folks to use now. I
So the Macs coming out will somewhat not be version 1.0 products. Perhaps something akin to v1.2 or v1.5 . Apple has been using these for a long time that means they have made progress. That not getting some half baked macOS sholved out the door too fast just to support a 'dog and pony show' pizzaz.
The DTK is for the masses. Vendors who have had super tight NDA beta boxes before will probably get access to not widely released hardware in the Fall sometime.
I doubt the Mac Pro version Apple Silicon is even out of finished design phase this year. (tape out probably some time late in 2021 ... maybe. ) There is nothing to hand to folks even inside of Apple let alone to 3rd parties. I would expect that the 27" iMac stuff that has at least one discrete GPU (either directly or through Thunderbolt ) to get some more "preview" talk time at WWDC 2021.
[qjuote]
Where their GPU work lands is important compared to Intel iGPUs. If they can make Intel look bad.
Great. [/quote]
It is going to be harder to make Intel look bad by the end of the year. Intel is about to make a pretty big jump.
https://www.tomshardware.com/features/intel-gen11-core_i7_1065g7-tested
Not what my argument was about though. My argument is that they should be talking about the PCIe facility which the A12Z doesn't need because it isn't a desktop processor. They should at least say something to the effect of: "Yes, we are making sure that folks using higher end GPUs and other PCIe I/O have a way forward, we just aren't ready to show that off yet."
The A12Z isn't Mac Apple Silcon. In one of the WWDC sessions recently one of the presenters mentions that the DTK doesn't exactly run macOS fully correctly ( that is a compatibility note in the "release notes" distributed with kit.
Getting super twisted about A12Z limitations is an overreach. No Macs are going to ship to customers with the A12Z.
Proably no Macs will ship with something labeled A14x either. If there are no discrete GPUs coming for 9-12 months then what are they talking about that is relevant to developers now for the next 2-5 months?
But even for the 27" iMac, they could really benefit from having PCIe lanes for a dGPU option.
but that isn't likely to be the first arm64 Mac out the door. I suspect the Mini is much higher in the priority queue than the 27" iMac. Apple may tackle the smaller screen iMac with their own. For the entry level , "edu" iMac they can certainly cover that in scope. Maybe the bottom of the Retina series too.
The mini's would make sense because lots of folks do build-test farms out of Minis. If there is tons more arm64 code to test then going to need lots of build-test farms for that code. That those build-test farms can do a ton of native iOS-iPadOS testing too is even more "extra" gravy on top. Apple would sell lots of those very quickly even if just brought the DTK up to "full Mac silicon". That would be the best desktop compliment to release with a moderately high laptop . The dGPU-less laptop is an even better fit.
dGPU sysetms is not what they need to get first out the door at all. Once in the dGPU space Intel's solutions have far more traction in competition.
Yes, I saw and understood the chart. I would be happy to have comparable performance for lower wattage. I'm not asking them to deliver a 200+W processor. What I'm saying is that going from a 4/4 design to a 28/4 design isn't just "slap more cores" and call it a day. Adding desktop-class PCIe and memory controllers requires extra die space as well. It all adds more complexities as the die size grows. It's a substantial jump from the types of SoCs they've made to date, and it'd just be nice for them to demonstrate that they intend to actually land there, and that they have a good shot at doing it.
Demonstrate how? Look if they already did this with the new 2019 Mac Pro in terms of saying "on board with the form factor". If they are doing something like that then dGPUs are a given. It coming. I don't see have there could be any reasonable disconnect there. There was no qualifying statement that they were only going to do a smaller subset of Macs in two year and would be dropping some. They basically said they'd transition the line up in two year. The Mac Pro is in the line up. So Mac Pro should be in the transition. There is not much to point to to say that it not given their baseline disclosure rules.
The bigger die is more complicated and will take longer to build out. That also means it is more probably not done. Which if it isn't largely almost completely done , also means Apple isn't going to talk about it in detail. that worked so well for them to violate that to Air Power. Not sure why they'd break the rules again now.
I mean, Apple's basically claiming that they can go from the A12Z to workstation class SoCs in 24 months.
No they are not. The A12Z is almost two years old. These DTK are probably a two year old design also. Add that 24 months to the 24-28 more months and you get a 4 year window. Getting a new CPU design out the door in 4 year is pretty regular. That is doable is assigned the manpower , simulators, and equipment to the problem.
If they use basically the same central core unit design for the iPhone as this larger chip then that lightens the resource loads. Need to tweak memory controller, PCI-e controller , USB, SATA , classic I/O handling , etc. but that is running concurrently with the iPhone cores than isn't a huge stretch goal. ( if pulling Thunderbolt4/USB4 inside that couldn't have started "early", but that can be punted to discrete controllers relatively easily. ).
If they actually can. Great. But this isn't like the Intel transition where the whole lineup they wanted pre-existed, and Intel's roadmap was not exactly a secret. Here we've only got Apple's word that they'll deliver. Apple's staking a lot on this, and I'd rather not see it become another AirPower issue where they announced too quickly.
I think is is a bigger jump not because of the technical problems entailed but how Apple tends to under resource top end Mac product development. That much smaller sales volumes probably tend to drive lower resource allocation.
I don't think it is a matter of an AirPower thing where it won't work at all. But they may take another step back from trying to go "head to head" with the higher end Dell/HP/Lenovo/Boxx workstations.
If Apple is too constrained on resources they could attach a small Apple Silicon SoC to the board where the T2 goes (and put it into a T-series mode ) and get an off-the-shelf Neoverse solution to toss into the Mac Pro. They don't "have to" do the bulk of large core count CPU design if they don't want to. That are ways of "mailing it in" that largely can just buy. Apple used to slap "G3" , "G4" , "G5" on chips that weren't called that in any other systems. They can get an Apple slapped on someone elese stuff if pay for it.
Given the stuff seen at WWDC I don't evpect it likely but making the date shouldn't be hard is they work at making the date if just lean on other folks stuff for bigger parts of the ARM core subsystem part.
It still took them 2 years from announcing they were going to change direction from the trash can to putting out the demo at WWDC last year. That's the lag we were talking about.
But they didn't had out a working prototype at the "pow wow" meeting in 2017. That is a significant difference.
It is not the lag talking about here at all. The gap between when had that early prodiuct range covering prototype ( probably on order of two years ago with a A12X sitting in same spot as A12Z doing not that much less) and spending another two years getting the Mac Pro silicon deeper into the design cycle before making the call on timing is indicative that it isn't the same at all.
Something for the mid-range Mac probably are at the tape-out stage (or very close). Once there and talking about wrapping up on the biggest one over next year or so then should know reasonaby well on track or not. Thrown in a 6 month "fudge factor" so ending before 2022 is over ( still in "about" two years zone) and should e doable with a highly dependable group. Even more so if farming out bigger chunks of the I/O subsystem to folks who already do that and just coupling via PCI-e ( discrete ASMedia and/or Intel chipsets for USB/SATA or Thunderbolt4+ )
I'm not even arguing against what you mention about the 2017 start date. But it's not a 2 year cycle to get something out the door unless you are hell bent on customizing the engineering design like Apple did with the 7,1. In some ways, it was worth it, but in this case, it was clearly perfect being the enemy of the good adding time to the project.
Apple inscribes "design by Apple in CA " (or Cupertino) on their motherboards. I was deeply puzzled back in 2017 when folks speculated that it would on be a couple of months to a new Mac Pro because they were just going to throw something into the old case and run down to Fry's to find SATA to slap in the machine. I thought it would be about 18 months. It is was bit longer but yeah.... they were probably going to dllberately design something.
Why would Apple not deliberately do something. It is is just a matter of getting making something for everybody and whipping lots of different products out the door then sure buy lots of stuff off the shelf and shoe horn in the compromises the save time and money. Apple wasn't trying to "save money" on the Mac Pro. The entry level price went up around 100%. They were going to be leaving more than a few folks behind.
pretty decent chance that this Mac Pro baseline has some broad thoughts weaved into it for the Apple Silicon. Those would have started around the same time. No dual CPU packages. Some tiny SATA could add with a small discrete chip if necessary. Extend the host USB provision out through the I/O card. Discrete TB controllers. Some one the GPU cards ( DisplayPort 2.0 will be on future cards ) The DisplayPort output from the GPUs cards flows into switched internal network ( so won't be too hard to add an Apple iGPU into a slightly bigger switch with a couple more inputs ).
The Mac Pro doesn't have any more "regular" USB sockets than a Mini or iMac . If have the basic ports support in the SoC for the iMac then can have basically what need for the Mac Pro. Mac pro probably needs some more PCI-e lanes out to fill in some "extra gaps' with perhaps a few more discrete I/O augments but have more space to put discrete components to "augment" that SoC.
There is work to do with more re-drivers because the many of the I/O channels on the larger board will need help at higher bandwidth settings ( PCI-e v3 versus probably v4 on first iteration. ).