In a blog post, Just outlines that he put both browsers to the test in two scenarios on the latest version of macOS. The first test was conducted on a virtual machine, and the second on a 2019 16-inch MacBook Pro with 32GB of RAM. In the first round of testing, Just simulated a typical browsing pattern of opening Twitter, scrolling around, and then opening a new tab with Gmail and composing an email.
Under that test, Just found that Chrome reached 1GB of RAM usage, while Safari used only 80MB of RAM. The two-tab test was only the start, however.
With 54 tabs open, Just found that Google Chrome used 24x more RAM per tab compared to Safari. Both browsers, according to Just, were free of any extensions, and this specific test was conducted on his actual MacBook Pro, not a virtual machine. Per his findings, Chrome used 290MB of RAM per open tab, while Safari only used 12MB of RAM per open tab.
While the results are stark, Just does say that Google Chrome is likely “going out of its way to manage its memory usage across tabs,” in efforts to keep the current tab “fast and responsive.” In his tests, Just finds that his own application, Flotato, a lightweight alternative to Chrome that creates apps based on webpages, used significantly less RAM than both Safari and Chrome.
Chrome is known to being a memory hog on Mac and Windows computers, an issue Google has recently attempted to solve.
With macOS Big Sur, Safari received significant updates that saw it further outpace Chrome. Apple says that Safari on macOS Big Sur is “50% faster on average at loading frequently visited websites than Chrome,” and that Safari provides up to one and a half hours longer of streaming video, and up to one hour longer normal web browsing on a single charge, compared to Chrome and Firefox.
Update: There are comments suggesting that these measurements may not be accurate. We’ll provide further updates as more information comes out.
This article, “Chrome Used 10X More RAM Than Safari on macOS Big Sur in Recent Test [Updated]” first appeared on MacRumors.com
Discuss this article in our forums