![]() ![]() ![]() I use both Chrome and Safari, and I don’t feel any marked speed differences between the two. In my opinion, it’s probably not worth basing your browser choice on benchmarks. While Chrome isn’t entirely to blame for heavy RAM usage (all those scripts it’s so fast at running take up space and resources of their own, and it can actually be tricky to measure system resource usage), it does have a reputation for being taking up a lot of space in memory. But for what it’s worth, most of the complaints I’ve heard from colleagues and strangers on the internet is that Chrome is a resource hog, not that it’s slow. Performance is a big deal when it comes to general web browsing - you don’t want to wait around when using a web app. With my computer’s weaker processor and less RAM, I didn’t hit the 300 mark the Google team says it achieved. That’s around a 30 percent difference on average, though obviously, there was a high amount of variability with Safari. Repeating it on my 13-inch M1-powered MacBook Pro with 16 GB of RAM, I got an even bigger performance delta: Chrome scored 252 runs per minute, plus or minus 8.6, and Safari got 185, plus or minus 46. Google notes that it ran its tests on a 14-inch MacBook Pro with a 10-core M1 Max chip and 64 GB of RAM. On lower-end hardware, the performance gap between Chrome and Safari can be even greater
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |