Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Is Yosemite more CPU/Memory hungry than Mavericks?

Hustler1337

Hustler1337

macrumors 68000
Original poster
Dec 23, 2010
1,856
1,612
London, UK
Hi guys,

as the title says, just wanted to find out how memory and CPU efficient or inefficient Yosemite is compared to OS X Mavericks. Is it more demanding or less demanding from your experience so far?

Thanks!
 
I don't have it installed but I will say DP1 is probably a poor measuring stick on an operating system's resource utilization. Its going to be a bit more bloated anyways, just because its a developer preview - the first one to boot.
 
Having been using DP1 for several hours now, switching apps back and forth, opening many tabs in finder and safari, playing high def movies in VLC, and general cocking about with Yosemite, my activity monitor says I'm using 10.86GB of 16.00GB, with 0 bytes of Swap Used...So, all in all, DP1 is a bit more of a memory hog than Mavericks 10.9.3...Not a huge issue if you have a large amount of RAM, but when you only have, say, 4GB RAM, having it use an extra 1.25 -> 1.5GB can have a substantial impact!

As for CPU, it's no better or worse than Mavericks 10.9.3, and this is all based on an Early-2011 MacBook Pro 15-inch.
 
Developer Previews have a lot of debug code in them, so it's hard to say whether OS X Yosemite is more resource hungry than OS X Mavericks until the final thing has been released.
 
I am running DP1 on a Mid 2013 Macbook Air with 4GB of RAM. I am using Memory Clean to see how much memory is being used and with my normal apps open, I am swapping regularly.

I might shut some background utilities off just to see what happens.
 
It would be logical to assume that it's a bit more hungry than Mavericks since it has so many transparent/blur UI elements. But the difference shouldn't be big.
 
I'm finding that it's pretty much the same as Mavericks, which is pretty good considering all the debug code and what not :D
 
After a little less than a week of usage, I'd say it's a right on par, but might have a slight bit more pull than Mavericks. However though, I'm sure the team at :apple: are working diligently to cleanup the interiors ;)
 
Hard to tell for the final product but I wouldn't recommend anyone using Yosemite for production purposes.

My new Macbook Retina 13, with 16GB of RAM is really clunky with scrolling right now. I'm also seeing random spikes in CPU.

Yes this is a beta. iOS 7 had far far worse problems then this during development so everyone's mileage will vary.

Don't expect to get the same performance right now that you would on your normal production mac
 
BasicGreatGuy said:
Seeing how Yosemite isn't at the beta 1 stage, the question is premature, in my opinion. It is an illogical question based on an illogical comparison.
Click to expand...

+1. It's far too early to compare the two.

----------
vigilant said:
Hard to tell for the final product but I wouldn't recommend anyone using Yosemite for production purposes.

My new Macbook Retina 13, with 16GB of RAM is really clunky with scrolling right now. I'm also seeing random spikes in CPU.

Yes this is a beta. iOS 7 had far far worse problems then this during development so everyone's mileage will vary.

Don't expect to get the same performance right now that you would on your normal production mac
Click to expand...

The first few iOS 7 betas were horrifically bad!
 
ram

i'm using yosemite and the ram usage is crazy
i got 16gb of ram and on a normal day, i have 4gb free..

i never get force closes, or hangs, but
i dont understand why theres so much ram usage

chrome seems to be the culprit, and i hate safari so... i guess we have to wait
i'm using the 64bit chrome


any ideas?
 
puccaso said:
i'm using yosemite and the ram usage is crazy
i got 16gb of ram and on a normal day, i have 4gb free..

i never get force closes, or hangs, but
i dont understand why theres so much ram usage

chrome seems to be the culprit, and i hate safari so... i guess we have to wait
i'm using the 64bit chrome


any ideas?
Click to expand...

Empty RAM is useless. Check the RAM Pressure graph in the Activity Monitor, if Green you are all good. OS X will keep closed apps in RAM for instance until it needs the RAM for something else. There is no overhead to doing this, if it needs the RAM it will take it.
 
It's because most of you are not able to understand how RAM is now used. Apple spoke about in back in the 10.9 launch.

Basically OS X is now using Memory pressure. How this work is the way each program uses as much memory as possible. When you switch to a different program it is suspended and the new program wil become active in the same way. That is why you have to look at Memory Pressure now instead.
 
satcomer said:
It's because most of you are not able to understand how RAM is now used. Apple spoke about in back in the 10.9 launch.

Basically OS X is now using Memory pressure. How this work is the way each program uses as much memory as possible. When you switch to a different program it is suspended and the new program wil become active in the same way. That is why you have to look at Memory Pressure now instead.
Click to expand...

A lot of this is actually incorrect from a technical point of view, but at the same time, it's not a bad way to explain it.
 
I had massive slowdowns until I turned off "Translucency". Now everything is running fast (faster?) than Mavericks!
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back