Is this for Haswell based rMBP or Ivy Bridge based rMBP?
How would it be Haswell, as they are not out yet
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Does Maverick give 15" rMBP extra battery life?
- Thread starter questionmark
- Start date
- Sort by reaction score
How would it be Haswell, as they are not out yet
I haven't tried the final with mine. But I can say it is closer to a realistic estimate on battery, maybe 8hrs tops. OS updates don't change how much battery the screen uses.
He talks about the power savings feature of deferrable interrupts.
That helps Haswells most because they are geared for really low idle power. They save more if they can stay asleep and thus it does more overall. Also Haswell has a really low power active state called i0x which helps for taking care of interrupts that don't call for much work. It will benefit Ivy Bridge too though but not as much.
What Quu doesn't accurately describe is the time frame. It is more accurate to talk about seconds rather than minutes. Intel needs for some power states a few milliseconds to enter and to exit. That is worth it even for 30ms of duration. But to defer interrupts that need attention for just a few dozen or hundred milliseconds is barely noticeable to the user.
On mobile devices and even desktop browsers JavaScript timers are usually automatically lengthened just to save power. IE10 allows that. One reason why Safari and IE are usually the most energy efficient browsers on each of their home platforms. Compared to Chrome, Opera & Co. Not because the code is more efficient but because they don't do stuff when it doesn't need doing.
The whole modern UI on Windows 8 exists to save power of the composited Aero Desktop. Apps only may run normal code while they are "in view". Otherwise they are frozen. There is a seperate API for background work if you need audio to keep playing. So no sloppy programming keeps the CPU active for no apparent reason and the the background API can be more easily babysitted by the OS.
Normal Window or OSX Desktop with Windows on top of each other everything is active the whole time, whether it just sits there or not. In Chrome background tabs even if they aren't in view can produce a ton of load. (just check the taskmanager) Afaik they don't freeze background tabs because it can break quite a bit of functionality and cause some odd behavior on rich websites. All that JavaScript stuff can produce lots of timer interrupts for nothing.
That helps Haswells most because they are geared for really low idle power. They save more if they can stay asleep and thus it does more overall. Also Haswell has a really low power active state called i0x which helps for taking care of interrupts that don't call for much work. It will benefit Ivy Bridge too though but not as much.
What Quu doesn't accurately describe is the time frame. It is more accurate to talk about seconds rather than minutes. Intel needs for some power states a few milliseconds to enter and to exit. That is worth it even for 30ms of duration. But to defer interrupts that need attention for just a few dozen or hundred milliseconds is barely noticeable to the user.
On mobile devices and even desktop browsers JavaScript timers are usually automatically lengthened just to save power. IE10 allows that. One reason why Safari and IE are usually the most energy efficient browsers on each of their home platforms. Compared to Chrome, Opera & Co. Not because the code is more efficient but because they don't do stuff when it doesn't need doing.
The whole modern UI on Windows 8 exists to save power of the composited Aero Desktop. Apps only may run normal code while they are "in view". Otherwise they are frozen. There is a seperate API for background work if you need audio to keep playing. So no sloppy programming keeps the CPU active for no apparent reason and the the background API can be more easily babysitted by the OS.
Normal Window or OSX Desktop with Windows on top of each other everything is active the whole time, whether it just sits there or not. In Chrome background tabs even if they aren't in view can produce a ton of load. (just check the taskmanager) Afaik they don't freeze background tabs because it can break quite a bit of functionality and cause some odd behavior on rich websites. All that JavaScript stuff can produce lots of timer interrupts for nothing.
Oddly enough, no. I have a life and things to do in it. Looking at the website and other information Apple have released as well as in-store, none discuss vast power improvements. They largely discuss improved notifications, a maps app and so on.
App Nap. Coalescing to reduce CPU usage by 70%. You're looking in the "consumer" section of the website. Click on Advanced Technologies and you'll see.
Last edited:
I just wanted to make it more simple to understand. Explaining to people the kinds of activity that happens from ms to ms is more difficult. Many people don't understand how software really works.
How would it be Haswell, as they are not out yet
Right I was not thinking because I have many things in my mind lately.
I would say thanks to ditched dGPU, there will be extra battery life...
And a lot less interest in me buying a MBP next time around.
I think the increase will be more significant on Haswell machines. Ivy Bridge doesn't have the fancy new power-saving features in the hardware. There might be some benefit for Ivy Bridge and earlier systems, but probably nothing to write home about.