There ARE some people using 1~2TB of RAM or more. It's not us to decide not to use them. Apple already added 1.5TB of RAM for Mac Pro so it's not even about WHY.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
M1 Max Quadro Mac Pro Leaks - The Alder Lake KILLER! 🤯
- Thread starter Adarna
- Start date
- Sort by reaction score
That’s the guy who promised he’d shave his beard if Apple didn’t introduce high-end MacBooks at WWDC this year. So, how come he’s still got the hipster beard?
There’s two of them - and the one that said this did. Hair grows back?
- Large scale 3D rendering. Complex models can consume a lot of RAM.
- Scientific modeling with large datasets.
I think you missed my point. The question wasn’t whether it was necessary to have 2TB of RAM. The question was whether it was necessary to have 2TB of unified memory. Read the rest of my comment, it might make more sense:
Last edited:
I have to agree. I actually watched this one and now wish I had that 15min back. The strained breathless delivery, the 100% certainty of things that seem to be opinion in the end, the arbitrary “10% for overhead” hand waving nonsense, the “Twitter agrees” as supporting argument.
There wasn’t any fresh insight at all— mostly just regurgitating stuff others, particularly Gurman, has said.
I feel like there’s a lot more insight and expertise in these forums.
Absolutely. I have seen some of his videos and the channel seems like an over eager amateur fanboy trying to appear sophisticated by pass on the stuff he would have read online here and there and creating video of a ‘leak’.
I laughed when he speculated about a single slot discreet GPU. Assuming full fat 128core GPU, the power draw should breach the 200w at a minimum.. perhaps even going as high as 280w (assuming the m1 max GPU ranges between 50-70w under sustained full load). No way will they be able to fit a single slot GPU in there with such power requirements
Not sure if performance scales so easily by daisy chaining processors. The chip to chip communication overhead will be a drag.
They're the only one talking about the rumors in a video format.
I think you are the one who missed my point. Unified memory is not magic and It still requires a lot of memory for heavy tasks. What you are saying is somewhat similar to this: 16GB Unified Memory is equal to 32GB RAM. What if the task size is huge which requires 32GB of memory? Also, it's better to have more than less. Since Mac Pro supports rack version, you also need to consider way more than 2TB of unified memory if the task size is huge.
Dont forget that unified memory also need to be used for GPU. You can not defy physics.
So many haters in this thread, lol. Apple Silicon is going to crush Intel, deal with it. Max Tech will do just fine with nearly a million subscribers that enjoy his content, compared with 10 or so people here who can’t stand it.
You still missed their point. That’s not at all what they were saying. They’re not arguing if people need 2TB of memory. They’re arguing if all 2TB needs to be unified memory.
This is something I’ve thought about too as a 4x M1 Max chip would result in 128 GB of ram based off of what we know. So my theory is Apple would also use off-package ram (as is done with Intel and AMD chips) to achieve 2TB of ram capacity.
Last edited:
I would calculate 10% for overhead... ;^p
What does a rack version of the Mac Pro have to do with more than 1.5TB of RAM, which is all either version of the 2019 Mc Pro ever supported...?!?
Any RAM beyond the UMA on the SoC / SiP / MCM would be secondary RAM, faster than swapping to the SSD, hereforth to be known as AppleCache...
While I don’t know what Apple will do, the memory doesn’t *need* to be integrated or on-package to be part of a unified memory system. Integrating lpDDR5 on-package lowers the power cost of the memory, but doesn’t intrinsically change anything else with respect to unified memory. Standard DDR5 modules could service a unified memory architecture. It’s just there would have to be a very large number of slots and they’d all have to be filled to make sure the bandwidth is high enough especially to run a GPU off of it. So there are downsides and again I don’t know what Apple will do, but DDR5 doesn’t *have* to be used as a separate pool in the memory hierarchy or forgone altogether.
I dont understand. Why not? Also, what if the task itself requires a lot of space then?
The idea is that the RAM would be split in two: 1) unified memory either lpDDR5 or HBM which has a smaller pool but larger bandwidth and feeds the SOC directly and 2) standard DRAM with a larger pool that could go to that 1.5-2 TB limit and would act like a cache for the huge data set. Technically not *necessary* but is an approach Apple *could* adopt.
This is where I was going, though whether the on package or off package memory is the cache is probably a matter of whether you view it like a processor cache or a disk cache.
Either way, this was essentially my point. The on package RAM has a number of key benefits-- power certainly, but more important in a desktop is the fact that this memory is lower latency than going out to big bus of DIMMs, and it is equally accessible to all the on-chip computation units so there's no need to push GPU or Neural data across a PCIe bus or whatever, and then pull the results back.
If you try to pool external RAM into the Unified pool, then you'll have address dependent access profiles which really complicates how the system will handle memory.
It seems more sensible to use off-package RAM as a distinct pool in the virtual memory stack. There's essentially two ways to look at it: you can think of package RAM as an L4 cache (or whatever) or you can think of the off package RAM essentially as a RAM-disk for swap. In the end, the difference is academic-- I'd imagine that the package would page less used memory off package, and page needed memory into the package.
This seems simpler than @crazy dave 's idea of massive bandwidth to the off package RAM which would be necessary to prevent slowing down the workload depending on address if it was all treated as a massive unified pool. The cores would execute against the on-package RAM at all times, it would retain unified access to all cores. The cores wouldn't have direct access to off-package RAM, it would be paged into the package before it was accessed.
You might see a difference if you set all cores to calculating a parallel running sum of the entire address space, but I'd suspect that 256GB is a sufficiently large local workspace to not be a major bottleneck for most workloads.
Last edited:
Just to push back at one aspect of this: on-package memory doesn’t necessarily have lower latency than normal DRAM, just much lower power for that latency.
So, Unified Memory Architecture...? ;^p
^^^ This, to avoid any issues with overworked SSDs down the road...?
I wonder if ~1 TB of unified memory, which would make an unusual amount of RAM accesible to the GPU, would allow coders to accomplish things not commonly possible with a workstation. That's even more than the 640 GB of GPU RAM in an entire $200k NVIDIA DGX A100 supercomputer module, which contains 8x NVIDIA A100 80 GB GPUs.
Is that true? I assumed when the bus starts getting longer than the clock wavelength, and then the buffers and drivers at both ends, there’s going to be a prop delay associated.
Not so much.
Part of Apple's performance advantage is that the RAM is so close to the SOC. Slots will negate that - the longer data path will make it hard to push the RAM so hard.
There's been talk of moving processing to the RAM chips for years; apple is halfway to doing this by putting the RAM on the same package as the SOC.
Apple aren't in the business of custom min/max tweaked configurations - they just work out a few options that make sense and you pick the closest one to your use case.
Is it "optimal"? No, but it does mean that Apple can get economy of scale for manufacturing which can help control their costs, and can help less informed consumers with decision making. There's no need to do a massive amount of analysis - you simply work out your constraint (ram or CPU or GPU) and buy a configuration that includes enough of THAT. It also gives the end user a more balanced machine, and enables apple to know what baselines are out there come software upgrade time.