593
this post was submitted on 18 Apr 2024
593 points (95.7% liked)
Technology
59534 readers
3195 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
It's not that you're wrong from a philosophical perspective with that, it's that you're factually incorrect. Memory addresses don't suddenly shrink or expand depending on where they exist on the bus or the CPU. Being on the SoC doesn't magically make RAM used less by the OS and applications, as the mach kernel, Darwin, and various MacOS layers still address the same amount of memory as they would on traditional PC architecture.
Memory is memory, just like glass is glass, and glass will still scratch at a level 7 just like 8GB of RAM holds the same amount of information as.....8GB of RAM.
The article actually quantitatively tests this too by pointing out their memory usage with Chrome and different numbers of tabs open.
Looks like you didn't read the article.
You should familiarize yourself with the architecture before commenting. The GPU is broken into several cores of the SoC, along with the roles of the CPU. The UM is not part of the SoC. However, data is passed from what could be referred to as the CPU to what could be referred to as the GPU without interacting with UM.
I'm actually deeply familiar with the architecture, and how caches, memory, and UM's work. I understand all of that. None of that changes the storage available. Having high memory bandwidth to load/unload memory addresses doesn't fix the issue of the environment easily exceeding 8GB. I also understand the caching principles and how you actually want RAM utilization to be higher for faster responsiveness. 8GB is still 8GB, and a joke.
Use your experience and analyze Apple’s M SoC before we continue this conversation.
A weeklong battery life, efficient cores, rapid response time, and great software environment make it a great choice......at 16GB for my needs. I will not recommend 8GB to any user at all going forward. It's marketing malarkey with no future proofing, degrading the viable longevity of the machine.
There's no conversation to continue. Glass is glass, and 8GB is 8GB, as well as being a joke.
If it’s great for your needs, the base model isn’t for you. You can stream video with have 30 tabs open in Safari and only use 4.6GB of UM on an M1 Mac. I just verified for you.
"Your powers are quaint, you must be popular with the children"
That’s on my M1 Mac Mini that I use as a server. I use an M2 with 16GB of UM for FCP, PS, and Logic Pro.