16gb vs 32gb of RAM in new MacBook Pro

[Elektrofone]

So I’m thinking of replacing my trustworthy late 2013 MacBook Pro with one of the new models but I’m struggling to figure out if I need 32GB of RAM or not.

I am a Motion/Graphic designer and work a lot with After Effects, Sketch, Photoshop and Illustrator.

I ran Activity Monitor today while I was working to see if it made a dent in the 16GB I have currently and everything seemed kosher, but i would like it to be futureproof.

 

[mr.anthonyramos]

So I’m thinking of replacing my trustworthy late 2013 MacBook Pro with one of the new models but I’m struggling to figure out if I need 32GB of RAM or not.

I am a Motion/Graphic designer and work a lot with After Effects, Sketch, Photoshop and Illustrator.

I ran Activity Monitor today while I was working to see if it made a dent in the 16GB I have currently and everything seemed kosher, but i would like it to be futureproof.

You answered your own question. Want to future proof it, get 32GB of RAM.

 

[iChase]

I regularly use upwards of 16GB of RAM in After Effects. My nMP at work has 64GB of RAM and the other day AE was gobbling up 52GB of RAM alone. If you're doing motion graphics, max that RAM. Especially if you want to be future proof.

 

[Juicy Box]

I ran Activity Monitor today while I was working to see if it made a dent in the 16GB I have currently and everything seemed kosher, but i would like it to be futureproof.

Was there any virtual memory being used?

16GB would probably be fine for you, but of course if you want to future proof it, 32GB would be the way to go. It would probably be easier to sell it with 32GB, if you ever decide to sell it.

It might be better to get it and not need it, than need it and you didn't get it. Although, it is an extra $400.....

 

[hellopupy]

Just depends on whether you think the $400 is worth upgrading to have that extra 32gb in around 4-5 year mark or would you rather have the $400 now.

 

[tu2thepoo]

Do some back of the napkin math. Take your longest-running task, the one you have to click the button and wait for the computer to finish processing. Then figure that any task that exceeds available RAM and has to go to virtual memory could be 5x-10x slower (or more). Multiply those two numbers by your hourly rate and compare that to the $400 cost.

For example, if I have to batch process a lot of images using Automator+pixelmator, it could go from a 5 minute task to maybe 45 minutes if I select too many images at once and exceed available RAM. If that’s a large part of your workflow, your total time for a project could be much longer. Is it acceptable to lose 5-6 hours over the course of a project (or whatever number you come up with)?

It may be less of an issue if you get paid for all of your time, it may be more of an issue if your invoices are set up front.

But bottom line, if 1) you’ve got the money, 2) spending it now doesn’t shortchange you on an essential piece of equipment later, and 3) your time is valuable enough that losing potentially hours is not acceptable, then get the extra RAM up front. You can’t upgrade it later.

 

[rdowty]

If you don't see yourself needing it in the next year or two I'd hold onto the cash. Maxing out a system and trying to keep it forever vs buying the off-the-shelf model, selling and upgrading a year or so sooner isn't a bad option since the one thing people never talk about when comparing Mac's vs PC's is they have good resale value.

You can only future proof so much. For instance the upcoming wireless standard is faster (I have gigabit internet at home and it would be nice to use it at full speed). The new display port will let you run an 8k display (which would be awesome when they're less than used car prices). They could do a 16" with a 4k display next year. Who knows...

 

[Fishrrman]

"If you don't see yourself needing it in the next year or two I'd hold onto the cash. Maxing out a system and trying to keep it forever vs buying the off-the-shelf model, selling and upgrading a year or so sooner isn't a bad option since the one thing people never talk about when comparing Mac's vs PC's is they have good resale value."

Quoted for truth.

The only folks who -should- "max it out" are those who actually use their MBP's for income, and who can "write down" the cost on their business tax returns.

And of course, those others for whom cost is no concern and will spend $5,000 on a laptop !!

 

[Ma2k5]

We need a 24 GB option to fill the gap!

/s

 

[Elektrofone]

"If you don't see yourself needing it in the next year or two I'd hold onto the cash. Maxing out a system and trying to keep it forever vs buying the off-the-shelf model, selling and upgrading a year or so sooner isn't a bad option since the one thing people never talk about when comparing Mac's vs PC's is they have good resale value."

Quoted for truth.

The only folks who -should- "max it out" are those who actually use their MBP's for income, and who can "write down" the cost on their business tax returns.

And of course, those others for whom cost is no concern and will spend $5,000 on a laptop !!

Well I do use my MacBook Pro for income. I am a freelance motion graphics designer and at the moment I do have a bottle neck somewhere in my workflow but I’m not sure if it’s CPU, Hard drive or RAM related. Or all three.

 

[johannnn]

In my little experience, those apps you mention can suck up quite a lot of memory. Are you like me and always keep all apps open with multiple files and +100 Safari tabs? Then 32GB should benefit you, if not today then it will tomorrow.
But like previous posters have said, if 16GB is enough today it might be better to just sell it and get a new one in a couple of years. That's what I do, get a new one roughly every second year (Macs have awesome resell value).

 

[Fishrrman]

OP wrote:
"Well I do use my MacBook Pro for income. I am a freelance motion graphics designer"

In that case buying the extra RAM makes sense -- particularly if you can amortize the cost of the MBP as a business expense.

Something about Adobe products, that I've read about (I'm NOT an Adobe user):
The "slowdowns" one experiences when using Adobe software with the Mac -- at least some of the slowdowns -- are due to problems in the Adobe "coding" itself. The software can be "inherently slow" at times.
I don't think "adding RAM" will make a difference in those cases...