While I can’t compare apples to apples between devices running Chrome OS and macOS, I can share a few key performance measures. The M1 blows away Intel-powered devices in browser benchmarksįirst, is the overall responsiveness the M1 provides. Let me elaborate on two key points as to why I think that. And after using the M1 MacBook Air, I’m more convinced than ever that Google should design a custom ARM processor for Chromebooks. Although I mainly use a Chromebook, I use various devices and operating systems to keep some perspective on the overall market. I replaced it with a MacBook Air powered by Apple’s M1 processor that I bought for $899 after a student discount. 16:19:38 DEBUG Webdrivers Completed download and processing of /Users/bytes/.A few weeks ago, I sold an old 2016 MacBook Pro that I wasn’t using much. 16:19:38 DEBUG Webdrivers Get response: # 16:19:37 DEBUG Webdrivers chromedriver URL: 16:19:37 DEBUG Webdrivers chromedriver version is NOT Apple M1 compatible. 16:19:37 DEBUG Webdrivers Apple architecture: Intel (mac64)
16:19:37 DEBUG Webdrivers Latest version available: 1.79 16:19:37 DEBUG Webdrivers Get response: # 16:19:37 DEBUG Webdrivers Making network call to 16:19:37 DEBUG Webdrivers Browser version: Chromium 1.81 16:19:37 DEBUG Webdrivers System call returned: Chromium 1.81 16:19:37 DEBUG Webdrivers making System call: 16:19:37 DEBUG Webdrivers Selenium::WebDriver::Chrome.path: /Applications/Chromium.app/Contents/MacOS/Chromium
16:19:37 DEBUG Webdrivers /Users/bytes/.webdrivers/chromedriver is not already downloaded 16:19:37 DEBUG Webdrivers Checking current version Or maybe I need to wait when (if?) a M1-specific chromedriver is released? Is there any way to fix this situation in webdrivers, and force Google Chrome with M1 architecture? It will certainly speed up significantly my test suite. Would it be because chromedriver doesn't officially support M1 architecture? And Google Chrome is forced to follow the same architecture? I checked and Google Chrome seems to use Universal Binary, so either Intel or Apple, but the wrong one is started. However, when I'm running my test suite, I can see in the Activity Monitor that the headless Chrome is not started with the correct architecture. I have a new Macbook M1, and I installed the M1-specific Google Chrome on my system to avoid using the Rosetta emulation. Maybe I'm not at the right place to submit this issue.
0 kommentar(er)
