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.
WindowServer Constant CPU Usage
- Thread starter r3volution11
- Start date
- Sort by reaction score
MrNomNoms
macrumors 65816
But at this stage the support isn't feature complete for all GPU's - IIRC Intel GPU's are ahead of the curve but that is probably more due to the fact that Metal for OS probably started off focusing on Intel GPU. I'd say that by the time the public preview is out there that the key features will be complete and it'll be a matter of fine tuning and bug fixing. Looking forward to seeing 10.11 to ship and hopefully Microsoft will promptly test to ensure that when Office 2016 is shipped for OS X that it is stable for 10.11.
Yea, there are a lot of doubts as to how complete Metal is in general as of DP1. We have at least 3 months to go for Apple to finish up its work but I have a feeling that Apple is generally happy with how it is now and will release El Cap even with incomplete Metal work to polish it up further in .x.x updates.
Yosemite and iOS 8 didn't feel complete until the .3 updates for both were released.
Apple should extend their 12-month release cycle to 18-month cycle instead, they really need the last 4 months to polish it up.
I think they also need to keep up with Windows... for me 10.11 and iOS9 are a disappointment. Back to the topic I hope WindowServer issue is fixed in the new beta.
MrNomNoms
macrumors 65816
I don't think pushing it out to an 18 month cycle would be the solution because as one pod cast I was listening to a while back noted (an ex-Apple engineer) that there is almost a guarantee that the 'gap' for testing will be filled with more features so you're back to step one again. It'll be interesting to see what happens when it comes to Metal implementation on nVidia given that it appears that the AMD and Intel seem to have a more flexible architecture that has allowed them to be further ahead than nVidia which might explain that, for all the faults of AMD, that their GPU design might end up showing through once Metal is fully implemented. It appears that at least with this cycle they didn't do any disruptive changes - mDNSresponder is back in action which gets the networking stack back in working order which should mean that man power isn't being spent fixing up bugs on the re-invented wheel.
Regarding the developer preview, is there some way to find out when it was actually built because if it was built and tested at least a month before the released then there is at least 2 months worth of work waiting to make its way out not to mention the work being done during the stabilisation of the developer build where the more risky stuff being merged into the main trunk and will appear in a later build. I'm confident that they'll get it all completed on time but I think there are far too many here expecting a feature complete build right out of the gate when in reality they're viewing a developer preview - a pre-beta build that is still too much in a state of flux for the enthusiasts to get their hands on to.
I'm on el capitan (early 2015 rmbp 13) and the WindowServer process uses around 0,2 when not doing anything and 10 - 20 when scrolling in apps and switching workspaces. Is this normal or is it using too much cpu? Anyone having similar stats?