this post was submitted on 13 Apr 2024
492 points (96.4% liked)
Technology
59390 readers
2518 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Here's how I see the advantages of soldered RAM:
The risk of physical damage is so incredibly low already, and energy use of RAM is also incredibly low, so neither of those seem important.
So that leaves performance, which I honestly haven't found good numbers for. If you have this, I'm very interested, but since RAM speed is rarely the bottleneck in a computer (unless you have specific workloads), I'm going to assume it to be a marginal improvement.
So really, I guess "smaller" is the best argument, and I honestly don't care about another half centimeter of space, it's really not an issue.
This is where you're mistaken. There is one thing that integrated RAM enables that makes a huge difference for performance: unified memory. GPUs code is almost always bandwidth limited, which why on a graphics card the RAM is soldered on and physically close to the GPU itself, because that is needed for the high bandwidth requirements of a GPU.
By having everything in one package, CPU and GPU can share the same memory, which means that you eliminate any overhead of copying data to/from VRAM for GPGPU tasks. But there's more than that, unified memory doesn't just apply to the CPU and GPU, but also other accelerators that are part of the SoC. What is becoming increasingly important is AI acceleration. UMA means the neural engine can access the same memory as the CPU and GPU, and also with zero overhead.
This is why user-replaceable RAM and discrete GPUs are going to die out. The overhead and latency of copying all that data back and forth over the relatively slow PCIe bus is just not worth it.
Do you have actual numbers to back that up?
The best I've found is benchmarks of Apple silicon vs Intel+dGPU, but that's an apples to oranges comparison. And if I'm not mistaken, Apple made other changes like a larger bus to the memory chips, which again makes comparisons difficult.
I've heard about potential benefits, but without something tangible, I'm going to have to assume it's not the main driver here. If the difference is significant, we'd see more servers and workstations running soldered RAM, but AFAIK that's just not a thing.
I understand the scepticism, but without links of what you've found or which parts in particular you consider dubious claims (ram speed can be increased when soldered, higher speeds lead to better performance, etc) it comes across as "i don't believe you, because i choose to not believe you"
LTT has made a comparison video on ram speeds: https://www.youtube.com/watch?v=b-WFetQjifc
Do you need proof that soldered ram can be made to run faster?
Yes, and the results from that video (i assume, I skimmed it, but have watched similar videos) is that the difference is negligible (like 1-10FPS) and you're usually better off spending that money on something else.
I look at the benchmarks between the Intel MacBook Pro and the M1 MacBook Pro, and both use soldered RAM, yet the M1 gets so much better performance, even on non-GPU tasks (e.g. memory-heavy unit tests at work went from 3-5min to 45-50sec from latest Intel to M1). Docker build times saw a similar drop. But it's hard for me to know what the difference is between memory vs CPU changes. I'd have to check, but I'm guessing there's also the DDR4 to DDR5 switch, which increases memory channels.
The claim is that proximity to the CPU explains it, but I have trouble quantifying that. For me, a 1-10FPS drop isn't enough to reduce repairability and expandability. Maybe it is for others though, but if that's the difference, that's a lot less than the claims they seem to make.
The video has a short section on productivity (i.e. rendering or compiling). That part is probably the most relevant for most people. Check the chapter view in YouTube to jump directly to it.
I think a 2x performance improvement is plausible when comparing non-soldered ram to the Apple silicon, which goes even further and has the memory on the die itself. If, of course, ram is the limiting factor.
The advantages of upgradable, expandable ram are obvious. But let's face it: most people don't need and even less use that capability.
Looks about the same as the rest. Big gains for handbrake, pretty much nothing for anything else. And that makes sense, because handbrake will be doing lots of roundtrips to the GPU for encoding.
On the package, not the die. But perhaps that's what you meant. On die would be closer to a massive cache like on the X3D AMD chips.
The performance improvement seems to be that Apple has a massive iGPU, not anything to do with RAM next to the CPU. So in CPU-only benchmarks, I'd expect the lion's share of the difference to be CPU design and process node, not the memory.
Also, unified memory isn't particularly new, APUs have supported it for years. It's just not well utilized by devs because most users have dGPUs. So I think the main innovation here is Apple committing to it and providing tooling for devs to utilize the unified memory better, like console manufacturers have done.
So I guess that brings a few more questions:
I guess we're kind of seeing it with the gaming PC handhelds, like Steam Deck and Ayaneo etc al, so maybe that'll become more mainstream.
Here is an alternative Piped link(s):
https://www.piped.video/watch?v=b-WFetQjifc
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.