I really doubt it. Choppiness is unfortunately present on even a lot of high end Macs. While not everyone seems to experience/notice the problem to the same degree (probably due to use case), it's definitely not restricted to slower machines.I have the base i5 2.0ghz and sometimes when I play YouTube video and do expose of all windows it feels choppy and not butter smooth. Like dropping frames of the UI animation.
I wonder if it would be butter smooth with a i7 2.4ghz.
I also have my screen resolution set to highest "More Space", could it be that and actually the iris' GPU and not CPU?
I really doubt it. Choppiness is unfortunately present on even a lot of high end Macs. While not everyone seems to experience/notice the problem to the same degree (probably due to use case), it's definitely not restricted to slower machines.
I've heard that it's related to the way that Apple draws the interface and that the underlying issues which cause choppiness have been resolved in iOS 10, so we can only hope the same fixes will be implemented in the next revision of macOS.
(Just for reference I used to experience chopiness at times on the 4Ghz/295MX 2014 Retina iMac I used to own....)
I have the base i5 2.0ghz and sometimes when I play YouTube video and do expose of all windows it feels choppy and not butter smooth. Like dropping frames of the UI animation.
When you do expose, the OS needs to redraw all the windows (and AFAIK, OS X does it in real time, so when you have expose on, ALL apps actively redraw everything, that is a lot of CPU work! yes, CPU, the GPU doesn't really care). The problem is not drawing per se, but the time needed to wake up an application which was currently in the background. This is also very application-dependent: a well-coded application should perform these actions very quickly.
There are some things that Apple could do to improve this, but all of them have drawbacks:
- have all apps active all the time (a real no go, kills performance and battery)
- keep a copy of every last window image in the resident VRAM, so that you can go into expose immediately (would need a lot of RAM that is wasted most of the time)
- display a placeholder image immediately and replace it by the actual window image when the app reacts to the redraw call — would result in fast animations but be potentially ugly
The only "performance degradation" I ever see on my 2016 nTB base MBP is using Expose. So would the 2017 models (the 15w TDP or 28w TDP CPUs?) improve upon this?
Nope. You will see the same thing on latest 15" MBP with 560 GPU.
@leman is right on this one.
But apparently, Metal 2.0 should help, so wait for High Sierra![]()