![]() ![]() Under full CPU load I suspect the percentage difference would be smaller, but still significant. The numbers below should help put that in perspective for you:Įven just browsing the web, the dGPU being on drops battery life by 35-60%. ![]() I'm going on and on about the dGPU because it's state can seriously impact battery life. Version 2.0.1 adds support for the 2011 MacBook Pros. Thankfully Cody Krieger's gfxCardStatus tool gives us exactly what OS X does not. There is no funny frame buffer copying going on, both the integrated and discrete GPUs have their own connection to the display.Īpple also fails to provide a way of turning off the dGPU by default-the best you can do is shut off the iGPU and just use the dGPU entirely. If you connect any external display to the 15 or 17-inch MacBook Pro that also forces the dGPU on, at which point both the integrated panel and external display are driven by the dGPU. FaceTime and anything using the integrated camera also require the dGPU, despite it being totally unnecessary. Even if you close all open images and just leave the Photoshop application open, the dGPU won't relinquish control. Actually open up an image and the dGPU takes over. Launch the application and you're still on the iGPU. The bad news is that even if you close all Chrome windows, the dGPU won't power down until you quit chrome entirely. In practice, the discrete GPU takes over control if your application uses any one of a number of frameworks-and some of the time, the dGPU simply isn't necessary.Ĭase in point, launching Chrome won't trigger a dGPU switch but the moment it encounters Flash the discrete GPU will take over. The 15 and 17-inch MacBook Pros have a discrete GPU that only turns on if you fire up an application that really needs it-at least that's how it is supposed to work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |