To the credit of Maxtech, they have a new video doing more RAM intensive workload. I shared the new video on my previous post.Ever think we need a way to flag posts as 'misinformation' or such in these forums?
Great point. No need to wear out the SSD - that’s what RAM is for. The question is, would it have a noticeable effect within a couple of years, by which time the machine may be upgraded anyway, once the total redesigns with an M2 or M1X or whatever they call it comes out?Beware of the swap disk space!
In most of the benchmarks performed on 8GB M1 machines, if Activity Monitor is shown, the swap space usage is always between 2,5GB and 4GB or even more. In my 10 years of being a mac user, I’ve never seen such big swap space being used unless I’m stressing my machine heavily, and that usage may be aging your SSD.
I have my choice clear, 16GB, even if it’s just for future-proofing my purchase.
Whew! Thanks for letting us know. We were losing sleep wondering what you were going to do. I’m staying away from AAPL until I hear you are ready to buy Apple Si Macs. //sI won’t buy one until all bugs are gone and Intel is finished.
“It’s just a computer, they’re all the same.”No, no and NO! Stop repeating that nonsense!
8 GB M1 = 8 GB Intel.
16 GB M1 = 16 GB Intel.
The M1 might have better performance and you might feel swapping slightly less, but swapping is still to be avoided. Swapping will ALWAYS be slower than a workload that has ram enough. Swapping is the last resort to ensure the computer doesn't have to run close down apps to stay running. Most tests of the 8 GB shows a fairly heavy use of swapping even in moderate workloads. So unless your workload is just a few tabs in a browser, some regular office stuff and watching Youtube, then you need to get the 16 GB version. And those of us which have a much heavier workload should really be hoping for a 32 GB and 64 GB option in future versions.
The M1 is impressive but you are not get a free launch. Your data and apps still require the same amount of ram - No ifs, ands or buts!
Whew! Thanks for letting us know. We were losing sleep wondering what you were going to do. I’m staying away from AAPL until I hear you are ready to buy Apple Si Macs. //s
Any user thats going to pounding on it that hard is going to be going "newer and better" is less that two years anyway. 8GB is fine for 95% of who will be buying this model.Great point. No need to wear out the SSD - that’s what RAM is for. The question is, would it have a noticeable effect within a couple of years, by which time the machine may be upgraded anyway, once the total redesigns with an M2 or M1X or whatever they call it comes out?
Yes, like any other new hardware you’re required to purchase it.yet, we have so many apps that don't work. partial list: https://isapplesiliconready.com/for/unsupported
not the point anyways. whether you wait for M1 to drop or not, you're forced to buy some form of ARM Mac.
that contradicts your earlier statement: "No one forced them to purchase them." ...?Yes, like any other new hardware you’re required to purchase it.
The DTK.that contradicts your earlier statement: "No one forced them to purchase them." ...?
DTK was mentioned after you said that statement. Your original statement was regarding the early adopters that didn't wait for 32GB variants of Macs.The DTK.
Get 16GB. In 5 years you’ll probably be using it.This is exactly what I was looking for, thank you MR! Was debating on getting the 16GB Mac mini but it may be good enough with just 8GB!
Second thought, might as well get the 16GB for future proofing.
But then what if I don’t actually need it and it’s a waste? Here we go again
Yeah, it's a shame you can't upgrade the ram.
IMHO On a closed system you buy the max RAM you can afford to insure compatibility for the maximum time.
I think we are both using the same term for two different things. And quite possibly, we are both correct.No, a page fault can occur even when you have plenty of RAM available. It is a part of the virtual memory management system. More technically a page fault occurs if the virtual memory page is not accessible. On x86 it is the MMU that is controlling how to react to page faults. Because it uses the so called Translation Lookaside Buffer to cache access to the pages the actual memory could still even be stored in the memory chip, but not in the TLB.
IMHO that is the safest bet especially if you are uncertain about how intensive your workflow is and if time is a premium.I haven't let any of my clients purchase new computers without 16GB of memory for the last 5 years. No reason I would change that with M1 equipped Macs.
I wasn't talking specifically about you. I was referring to a number of people who proclaim nonsense such as 8 GB M1 = 16 GB Intel and that believe the M1 has some kind of "magic sauce" that all of the sudden makes your files take up less space when loaded into memory.At no point have I said it was magic. I have specifically stated it was not.
I have said that it seems the M1 Macs can get by with less than Intel systems in general. Even you have to admit some people seem to think of it as a badge of honor that their RAM (SSD, processor speed, screen size, color depth, temperature, power draw, battery life, trackpad sensitivity, headphone jack, webcam resolution, or whatever) needs somehow exceed those of the "mere mortals" around them.
The number of tracks you can run in programs such as Logic is almost purely CPU based, unless you are using some kind of ram intensive plugin. The M1 has some crazy performance and seems to have a very low memory latency, which gives it some awesome performance characteristics. It doesn't mean that the computer uses less ram to load data into memory compared to the Intel based Macs.I have specifically stated an example of an absurdly large music project someone created to try and crash an M1 base model mini, only to have it keep running.
It isn't magic, but some of the rules are clearly a bit different than we are used to. Until we see a chance to test your specific use case (for something reasonably expected of a lowish end machine), it is unfair to say "there is just no way..." because they have clearly been punching above their weight class.
The M1 is very very impressive - I fully agree. But it still doesn't mean that the M1 can load a 100 mb Photoshop file into less memory than the Intel based Macs can. The performance stems from the fact that the processor itself is close to previous top-models and for single core, surpasses them. It stems from the fact that the processor as we used to think about it has changed, because it's no longer just about cores but about all the specialized chips that is bundled in to the package, such as ML cores, HEVC encoding acceleration etc. The fact that memory is so closely attached to the CPU cores also speeds up loading and avoids some copying processes. This is all the stuff that makes the M1 extremely impressive. But it still doesn't have any significant influence on the amount of ram you need for loading X amount of data. The SSD might be fast so you feel the swapping less, but the SSD is already fast in the latest Intel versions and you don't feel the swapping in those much either. Until a certain point then you will start feeling it, both on Intel and the M1.Everyone keeps saying, "yeah, but it will never handle my needs," but they do not know this if they haven't tested it. Yes, I will spot you that if you are running your own personal Matrix simulation of reality with 128TB of RAM and a 60 Petabyte SSD Octo-RAID 20 configuration powered by dilithium crystals, it will not run on a MacBook Air. (What laptop were you running it on before the announcement?). So far, I keep looking back and forth between the M1 and my 2019 16" MBPro that is maxed out on everything but storage (edit, and only 32GB of RAM, not 64 - oops), and the hand isn't writing on the wall, it is punching me in the face. I keep waiting to see where the M1s are going to really, actually fail (not speculative fail, measured tested, benchmarked fail). It hasn't happened yet that I have seen. Maybe tomorrow.
I wasn't talking specifically about you. I was referring to a number of people who proclaim nonsense such as 8 GB M1 = 16 GB Intel and that believe the M1 has some kind of "magic sauce" that all of the sudden makes your files take up less space when loaded into memory.
Actually it does per efficiency. Again the way the M1 and software interact with each other changes the whole RAM dynamic. This is why an iPhone runs rings around an Android phone even though they are both ARM.TL;DR
The M1 is very impressive but doesn't significantly change the amount of ram that is needed to load X amount of data. In the end it's a computer so get the one that suits your needs. Maybe you can get by with 8 GB, but that doesn't mean that others wont require 16 GB or even more.
Again you are ignoring the fact that efficiency totally messes with this premise. A chip-software combo with twice the efficiency needs half the RAM, pure and simple.Personally I would never get a computer with less than 16 GB of ram in 2020 unless I was a super casual user. I'm hoping to be able to get an M1 or whatever it might be called at that point, with 64 GB of ram. But thats for my personal use - That doesn't mean it's the right config for everybody else.![]()
What you are talking about affects the performance NOT the amount of ram needed to load X amount of data. The speed of allocating NSObjetcs is performance, not how much data can be loaded before you need to resort to swapping and other fall-back methods.Again you are ignoring the fact that efficiency totally messes with this premise. A chip-software combo with twice the efficiency needs half the RAM, pure and simple.
I used a car analogy tooJust for fun, let's use a car analogy to compare the 8 GB and 16 GB version.
The 16 GB version is like an Audi RS 6 Avant. It's very very fast and since it's a wagon it can carry a lot of stuff.
The 8 GB version is like an Audi RS 5. It's also very very fast but it can't carry the same amount of stuff.
So for workloads where you need to move a lot of stuff, the RS 6(16 GB) will be faster. The RS 5(8 GB) version can move the same amount of stuff, but it will have to drive multiple times back and forth, making it take longer.
For situations where you don't need to move a lot stuff, you just need to move it fast. They will be more or less identical in performance.
😁
Your analogy just doesn't hold up. Amount of ram doesn't have anything to do with "mileage". 100 MB of data, takes up 100 MB of data. It doesn't matter if the processor is from Intel, AMD, Apple or somebody else. In your eagerness to confirm your own belief that the M1 is kind of magic, you are misunderstanding vital parts of how RAM works and how the computer utilizes it.I used a car analogy too
It is equivalent of a gas guzzler that gets 10 miles per gallon (Intel) and a more fuel efficiency vehicle that gets 20 miles per gallon (M1) both of which have a 20 gallon tank (certain amount of RAM). The gas tank in the 20 miles per gallon vehicle doesn't "magically" double - it is just more efficient with that 20 gallons of gas.
CISC got bloated with instruction sets that rarely were used and ARM was created to address this. - Intel is in serious trouble. ARM is the Future. The really funny thing is that video was posted Dec 21, 2018. Now look at time stamp 18:27 and then look at 18:36 - 7 Core GPU, 8 Core CPU, Neural Engine. Now where have we seen that recently? Why the low end 13-inch MacBook Air (Apple M1 Chip with 8‑Core CPU and 7‑Core GPU)
"Within the next 24-months we will see Apple transition their family of products, that have so far relied on Intel chip to their own ARM based custom SoCs." Don't know how this guy called it but he did.