GFXCARDSTATUS Use ?

[dk808]

Why is safari causing it to switch to the dgpu though?

 

[MagicBoy]

But like some one said if it is an APP which is supposed to use dGPU and if you have forced iGPU through GFXCARDSTATUS the overall performance would be laggy.

I was verifying the forked v2.4.3i functions correctly after previous postings relating to the original developers v2.3. My comment is unrelated to any remarks about GPU performance.


Now that you've opened that can of worms... laggy is a terrible word, I don't know where it came from. I find the iGPU performance on my machine to be perfectly fine, outside of gaming. I see no need why certain apps switch to the dGPU, for example iPhoto.
[doublepost=1482230410][/doublepost]

Why is safari causing it to switch to the dgpu though?

Most likely a plugin. Flash used to switch the dGPU in on my 2011 MBP.

 

[Creep89]

I agree. Or lets take Parallels into consideration. No need to switch to dGPU for some basic stuff you do in VMs. Especially not when you are running on battery.

 

[MagicBoy]

Parallels is another good case. My machine runs a Windows VM lightning fast on the iGPU, the dGPU makes no discernible difference other than increasing the noise and decreasing the battery life! It still emulates Windows Aero and runs older games with the same performance.

 

[augustya]

I was verifying the forked v2.4.3i functions correctly after previous postings relating to the original developers v2.3. My comment is unrelated to any remarks about GPU performance.


Now that you've opened that can of worms... laggy is a terrible word, I don't know where it came from. I find the iGPU performance on my machine to be perfectly fine, outside of gaming. I see no need why certain apps switch to the dGPU, for example iPhoto.

iPhoto without the GFXCARDSTATUS switches to dGPU in the 2016 15" rMBP ?

 

[MagicBoy]

iPhoto without the GFXCARDSTATUS switches to dGPU in the 2016 15" rMBP ?

This is what I stated :

2.4.3i works fine on the late-2013 rMBP.

I don't own a 2016, I'd rather keep the better older machine!

As regards the question, I'd expect the 2016 to switch to the dGPU as GPU switching works the same on all MacBooks. If an application requests certain functions it gets flagged as High Performance and ensures the dGPU is used.