10/16/2021 0 Comments Google Chrome For Mac Mini
Users enjoy its fast loading speed, cross-device integration, and tabbed browsing.Let me preface this by making it very clear that I’m not a fan of Google Chrome. Google Chrome is the most widely used web browser in the world. The worlds number 1 browser. Many users have reported that this does work and that after removing Google Chrome from their machines, everything got a lot faster.Download Google Chrome for Mac & read reviews. Needless to say, Google is the default search engine in Google chrome.The website includes information on how to completely get rid of Chrome and its updater from your Mac to get your performance back, and went as far as calling it “malware” (that word has since been removed). Although safari is an inbuilt browser, Chrome is also one of the most used browsers on mac.It seems to handle things such as uploading crash reports if any are available, as well as checking for updates of Google’s apps, such as Chrome. These are not services that will keep running indefinitely, they are only started periodically to check for updates or when a Google app wants to talk to them, which makes the claim that they slow down WindowServer even more interesting.As to what this updater agent does, I’ve done some basic reverse engineering by statically analyzing the binaries involved using Hopper. The other one, “Keystone XPC Service” is started only when a Google app wants to check for updates itself, on demand.
Google Chrome Mini How To Completely GetI don’t see this as a confirmation of the problem, given that the difference is negligible (way below what would cause visible performance issues).Apart from that, the entire claim that a process which runs once per hour would cause a completely unrelated system service to have high CPU usage is wild. Without Chrome and its updater installed, it used about 49s. I’ve used the first 30-minute window of the Instruments session to measure the CPU usage of WindowServer in each scenario.As you can see from the comparison above, with Chrome installed, the WindowServer process used about 50s of CPU during the test window. The machine was plugged into an external display, no other apps were actively doing anything other than basic background tasks during the tests and I also left caffeinate running to prevent the machine from sleeping.Using Instruments, which lets you observe software metrics such as CPU usage over time, I recorded two sessions: One with Google Chrome installed and another one with Google Chrome and the updater services uninstalled. The tests were performed on a 2019 16” MacBook Pro with a Core i9 processor and 16GB of RAM. Is the Google Chrome updater actually the cause of this WindowServer high CPU usage that people are seeing?This was the main question I set out to answer during my tests.
0 Comments
Leave a Reply. |
AuthorSteve ArchivesCategories |