Dr Huge Longjohns wrote:My mac tells me a Logic project is using 2.6gb of RAM but everyone else is saying that a total of 8gb isn't enough to run Logic and OS simultaneously.
I didn't did it isn't enough to run Logic, I said "I don't recommend it", for the reasons outlined.
Yes, Logic is "using" that amount of RAM, but that doesn't mean that amount of RAM is actual RAM. If the system is low on available RAM resource, it will swap to disk. As far as Logic is concerned, it has "2.6GB of stuff it's stored" but it doesn't necessarily know *where* that data is. The system *might* have written the entire thing to disk, and might need to read bits of it from disk every time Logic access or changes some data... Or it might have written some *other* system/app memory to disk, to make space for Logic's RAM requests.
The system is designed to not enforce arbitrary limits. You can potentially run a program and have it request more RAM than is actually physically there on your system - the system will then mange a large swap file on disk that behaves as if it's (slow) RAM. Things will still work, but they'll get slow and your computer will start to feel bogged down.
Let's have a look at Activity Monitor on my (16GB) MBP, which has recently rebooted. I only have Safari (with this web page) and Activity Monitor open (but I do also have quite a few utilities running that I always have).
Physical Memory: 16GB. Cool.
Memory used: 9.5GB (whoa - with just the system running, and Safari and a few running utilities, I've already used *more* than the 8GB that people are suggested is fine... And I haven't even run a big app and starting working in it...)
Swap used: 0 bytes (My system hasn't swapped anything to disk, so it's all operating from RAM).
Now - those memory figures are *guidelines* as things are more complex, but you can take them as a general picture of what's going on memory-wise. If you're running 8GB now, it's worth monitoring this when you boot up and as you're working to get an idea of how much resources you typically need to get your tasks done.
For me, the idea that I can start my hypothetical (8GB) system, and before it's even done anything, is *already* on the edge of running out of breathing space and having to resort to swapping to just keep going is not a good start for a complicated, real-time performance and resource heavy application like a DAW to run in - imo.
Anyway, that's my recommendation, and has been for a while now... ymmv