I did already, the result is the same. This has nothing to do with the GPU. Like I said earlier, my late 2015 5K iMac does the same thing. This has more to do with Sierra than anything else. I noticed a big difference after I upgraded from El Capitan last week.
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.
Video of iGPU comparison of 2016 vs 2015 models
- Thread starter dark_mark
- Start date
- Sort by reaction score
I picked up the laptop yesterday so it's done doing any indexing. Forcing dGPU is possible but then you will be getting a 4 hour battery life.
I have a feeling the reason the 13" does not lag is due to the onboard cache the 540 has, the 530 does not have this as the dGPU has it.
I agree forcing the dGPU is not helping the stutters in finder. But when forcing dGPU the lag in Chrome and in Microsoft Outlook and in Google photos is gone.
I am thinking that Apple doesn't let it's own internal apps such as finder and stuff use dGPU so that users don't blame the week iGPU.
oh well, yet another reason to consider this release a compromise too far. these are definitely transition machines. there should be a mid 2017 update that hopefully clears all these issues out. and also another reason to consider replacing my old Air with another Air and it's non-retina, non-battery killing screen.
Why? They are throttling Verizon iPhone 7, so that users don't notice a performance difference with AT&T model.
They may have done the same with Macbook Pro 15. If forcing dGPU provided such a drastic difference in UI animations then it's possible they may have decided to always use iGPU for finder even when dGPU is enabled. Just so that users don't notice a big difference in performance. But this is just my speculation with no proof.
Fact is, the laptop stutters, in Google Photos, Microsoft Outlook, in heavy websites, in finder, in large PDF files, in Mission Control and etc.
I guess I won't be aimlessly scrolling up and down in my Applications folder on my new 15" Macbook Pro. That's a shame, because I was really looking forward to that.
You said they make finder not use the dgpu because people would be upset with the igpu. That makes no sense at all.
I just tried the base 15 at Apple Store. GFXcardstatus was installed so I can check the state of graphics card. Everything was butter smooth under iGPU.
Can't wait for my 15 to arrive.
Can't wait for my 15 to arrive.
You might be running some app(s) thats causing OS to switch into dGPU then. Btw, new 13's iGPU should be nearly twice the speed of 15's iGPU.
Likewise. These posts are informative and give better insight into Apple's hardware choices.
People attacking you are doing just what you said, defending the fact they bought one (which is fine, I hope anyone who does enjoys it).
So many damn issues with these things. All I wanted was a Skylake 15" with a decent iGPU and no dGPU with 10 hours of battery life. That is all I wanted, so now I am stuck with getting a laggy 15" with failing dGPU's (see various threads) or a smaller screen with less powerful dual core 13", that has even worse battery life. Christ Apple, what were you thinking with these things. This is my first mac and I said no matter the price or features I will buy it, but d*** they are making it hard. I can't be the only one, who thinks this. Really hoping these issues are being blown out of proportion or can easily be fixed by Apple.
#EndRant
#EndRant
Not everyone has these problems. Just wait until you get yours and see for yourself
Not to discount your words, but it doesn't divide by task. Certain things trigger a switch, and it can remain on discrete graphics even if the system isn't under load. It has always worked this way.
May wanna check out what's wrong with your 2016 MBP as no other users have reported the same Finder Applications UI lag as yourself, do update if you can solve that issue!
If this doesnt happen on exactly 100% of all new 2016 15 macbook pro your statement that its the 530s fault is unvalid.
And since most ppl say they dont have it means youre wrong and theres something wrong with your hardware or you could have got some "bug" in your software install, especially if you restored it from a backup
And since most ppl say they dont have it means youre wrong and theres something wrong with your hardware or you could have got some "bug" in your software install, especially if you restored it from a backup
Thekev is perfectly right. It does the same on my MBP and you can monitor the switching behavior with gfxCardStatus.
Even some webpages will trigger the dGPU and certain processes (iTunes, Photos App, Lightroom, Photoshop) will prevent from switching back to iGPU.
If you believe the marketing gibberish on Apple's website, well, do you believe that the MacPro is still a state of the art computer?
Even some webpages will trigger the dGPU and certain processes (iTunes, Photos App, Lightroom, Photoshop) will prevent from switching back to iGPU.
If you believe the marketing gibberish on Apple's website, well, do you believe that the MacPro is still a state of the art computer?
I don't think this problem is caused by the difference in iGPU performance, the test is too trivial. Basically any iGPU made in the past 3 years should be plenty fast to scroll a grid of icons, even in hidpi mode.
I'm not saying there isn't a problem, but it could be caused by something else (OS version? heavy background activity? touch bar? throttling for some reason? some hardware fault?).
Think it's more of a misunderstanding. thekev meant that even if you're not using an intensive task, an app running in the background may leave the dGPU activated. So both of you are right to say that a not-intensive application is not going to run the dGPU, but an app in the background may not allow the mac to switch back to the iGPU.
[doublepost=1479647903][/doublepost]
Yeah I guess I have still been unable to conclusively determine if the HD530 is going to be sufficient for all other UI tasks, over the Iris Pro 5200. And I sure hope it is sufficient (or even more than sufficient!)
[doublepost=1479647903][/doublepost]
Yeah I guess I have still been unable to conclusively determine if the HD530 is going to be sufficient for all other UI tasks, over the Iris Pro 5200. And I sure hope it is sufficient (or even more than sufficient!)
The new screen has variable display refresh rates to save power. A low refresh rate can make scrolling look jerky.