Nice, an update well received by enthusiast.
Speedometer 3.0: A shared browser benchmark for web application responsiveness
121–130 of 183 posts
Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness
#122Earlier quoted context omitted.
I ran v3 on my machine while listening to "Voyage" by "Yahel & Eyal Barkan" in Chrome and doing a bunch of background stuff. The background stuff took up about 20% of my CPU. While testing, the music played perfectly without any buffer underrun pops. Ran it in each browser one at a time while the music played in Chrome. Chrome 122.0.6261.112: 21.3 +/- 0.64 Edge 122.0.2365.80: 20.1 +/- 0.78 Firefox 121.0.1: 18.5 +/- 0…
Any track plays completely garbage on Edge. The beat skips, the sound cuts off. This one for instance: https://deepsid.chordian.net/?file=/MUSICIANS/F/Fate/World_R... I think Edge's problems come from some kind of power efficiency setting, not necessarily performance-related. (Like a low-granularity JS timer, or something like that) EDIT: Turning off all efficiency settings on Edge didn't make any difference: 11.0
Do you have your Windows power plan on Performance? Maybe thats the difference?
Definitely would be a bummer if web audio didn't work reliably on the default power plan (which is Balanced iirc)
Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness
#123Posting just because nobody else has posted one this high: Mac mini M2, macOS 14.4, Chrome 122: 30.2 ± 1.6 Good ol' Apple Silicon.
I got 35.7 ± 2.3 on a MacBook Pro M3, Chrome 122.
33.3 with an Intel 14900k and Ubuntu. And people will sit there and try to tell you that computers aren't getting faster any more.
Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness
#124Earlier quoted context omitted.
Interop is only a tiny subset of the entire suite of WPT tests, and it only contains tests that all vendors agreed upon, so no browser will look bad in Interop. If you look at the full WPT test suite [1], you'll see that Safari is by far the one failing the biggest number of tests, i.e. the most buggy browser. The Safari team likes to use Interop to trick people into thinking Safari is as good as the others. It's jus…
For a less biased result, use Stable: https://wpt.fyi/results/?label=master&label=stable&aligned > If you look at the full WPT test suite [1], you'll see that Safari is by far the one failing the biggest number of tests, i.e. the most buggy browser. In Safari's case, most WPT test fails mean "hasn't been implemented yet". > Interop is only a tiny subset of the entire suite of WPT tests, and it only contains tests tha…
"Browser-specific failures are the number of WPT tests which fail in exactly one browser." From wpt.fyi
In other terms, WPT test failures for Safari means Safari has bugs or unsupported features that both Firefox and Chrome do not have.
As for Interop, it focuses on a specific, very limited areas, like "scrolling" or "subgrid" and is in no way representative of the overall feature set of a browser.
So no, contrary to what you're implying, it's not that Chrome is too advanced, or doing too much, it's really Safari that is buggy and lagging behind both Chrome and Firefox (by a lot).
Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness
#125Earlier quoted context omitted.
For a less biased result, use Stable: https://wpt.fyi/results/?label=master&label=stable&aligned > If you look at the full WPT test suite [1], you'll see that Safari is by far the one failing the biggest number of tests, i.e. the most buggy browser. In Safari's case, most WPT test fails mean "hasn't been implemented yet". > Interop is only a tiny subset of the entire suite of WPT tests, and it only contains tests tha…
"Browser-specific failures are the number of WPT tests which fail in exactly one browser." From wpt.fyi In other terms, WPT test failures for Safari means Safari has bugs or unsupported features that both Firefox and Chrome do not have. As for Interop, it focuses on a specific, very limited areas, like "scrolling" or "subgrid" and is in no way representative of the overall feature set of a browser. So no, contrary to…
> In other terms, WPT test failures for Safari means Safari has bugs or unsupported features that both Firefox and Chrome do not have.
Yep! Safari is not the browser for people who need cutting-edge features, especially not for ones still at the proposal stage.
Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness
#126Try it here: https://browserbench.org/Speedometer3.0/ Very unscientific results using a Mac Studio - Chrome: 20.4, Safari: 17.9, Firefox: 20.1. Safari on an iPhone 13 Pro Max - 16.5.
On my Early 2015 MBP
Safari 17.4. : 5.52
Chrome 122 : 6.25
Firefox 123 : 7.26
The results pretty much confirms my general feeling about how the browser behaves on my machine as well. Where Firefox being the fastest.
And 22.5 on my iPhone 14 on iOS 17.4
That is my smartphone is ~4x faster than my laptop.
Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness
#127Platform Wars Results
Samsung S24 Galaxy - 13.8 (very new, with the good processor)
iPhone 13 Mini - 22.3
iPhone 15 Pro - 23.1
MBA M2 - 24.2 (Safari)
Win 11 i9-13950HX - 26.8 (Edge)
Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness
#128iPhone 15 Pro Max; iOS 17.4; Safari: 26.2 in a private tab Pixel 8 Pro; Android 14 QPR2; Chrome: 9.47 in an incognito tab
I was debating between a Galaxy S24 and a Pixel for an Android test device. 13.8 vs 9.47 on a Pixel is not a good result for Google's custom chip.
Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness
#129I tested this with Firefox stable release and Brave stable release, 3 runs on each. Same exact extensions across both. Highest scores across tests: Firefox: 6.34 +- 0.31 Brave: 11.3 +- 0.37 on Ryzen 9 7940HS + RTX 3060 mobile Which really sucks since I highly prefer Firefox but this past week I've been trying out Brave and I think its noticeably faster and smoother to me. Even with the reduced speed I'm still swayed…
What's your score in Firefox with extensions disabled?
Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness
#130Try it here: https://browserbench.org/Speedometer3.0/ Very unscientific results using a Mac Studio - Chrome: 20.4, Safari: 17.9, Firefox: 20.1. Safari on an iPhone 13 Pro Max - 16.5.
I'm getting 27.7 in Safari 17.4 on an M1 Pro MacBook. I'm puzzled how you got so low on a Mac Studio.