Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Speedometer 3.0: A shared browser benchmark for web application responsiveness

browserbench.org

Post reply on HN
Print view View original

81–90 of 183 posts

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#81

Post by rezonant »

sedatk wrote: post #79

On my machine, Firefox got 12.3, and Edge (Chromium) got 12.8. I don't believe that the performance characteristics of these two are that close unless I'm missing something. For example, audio players on Edge stutter a lot while Firefox plays them smoothly. An example is: https://deepsid.chordian.net/ I believe Edge is slower not because Chromium is slow, but because of Microsoft's overreaching efforts on energy cons…

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.75

Machine specs: Intel Core i9 12900k (24 core) / 64GB RAM / 3080Ti / Windows 11 Pro 23H2

After finishing the tests, I played that same song on Firefox and Edge. Both Firefox and Edge played it perfectly.

> audio players on Edge stutter a lot while Firefox plays them smoothly

I'm curious about what could be leading to this inconsistency as I use Web Audio for a number of projects, so I have a bit of a vested interest. It is notoriously easy to do WebAudio wrong or to do just a bit too much computation which leads to buffer underruns (pops). It also may have a lot to do with specific tracks on DeepSID, could you share some tracks that perform inconsistently for you?

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#82

Post by CharlesW »

kouteiheika wrote: post #76
CharlesW wrote: post #39

Earlier quoted context omitted.

Is it though? https://wpt.fyi/interop-2024

> Is it though? In my experience it's the buggiest browser out of the big three, and is often missing basic features like e.g.: https://caniuse.com/?search=opus Supported in Firefox for *12 years* now, in Chrome for 10, still no support in Safari. They only "support" Opus audio in their special snowflake '.caf' container, which is super buggy and the last time I checked no open source program could even generate Opus…

> You shouldn't have to do this to have cross-browser high quality audio!

You don't, because HE-AACv2 is as universal as MP3 and better than Opus at low bitrates.

That said, Safari for macOS and iOS plays all the examples at https://opus-codec.org/examples/ except the last.

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#83

Post by freediver »

atlas_hugged wrote: post #67

In iOS, all browsers (at the moment) use Safari under the hood. Imagine my surprise to see these noticeable differences in some of them. Vivaldi:12.2 Brave:18.1 Safari:18.2 Chrome:19 Firefox Focus:21

This is because browsers on iOS do not 'use Safari' but use WebKit and there is huge amount of browser app software built on top of it, which will contribute to variance on benchmarks (and also to these being very different browsers ultimately).

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#84

Post by SushiHippie »

mattlondon wrote: post #52
tdudhhu wrote: post #25

On Firefox mobile I got a score of 3. So while Firefox is now super fast the performance of webapps might still be very bad on mobile. And I think this applies to all modern browsers: they are fast at rendering very slow webapps and websites.

Approx 6.3 and 6.7 in chrome and Firefox respectively on my low-end Pixel 6a

Weird I have the Google Pixel 8 Pro and get a score of 4.83 in Fennec and 6.61 in Vanadium (hardened chromium fork).

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#85

Post by sedatk »

rezonant wrote: post #81
sedatk wrote: post #79

On my machine, Firefox got 12.3, and Edge (Chromium) got 12.8. I don't believe that the performance characteristics of these two are that close unless I'm missing something. For example, audio players on Edge stutter a lot while Firefox plays them smoothly. An example is: https://deepsid.chordian.net/ I believe Edge is slower not because Chromium is slow, but because of Microsoft's overreaching efforts on energy cons…

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

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#86

Post by hedgehog »

CraftThatBlock wrote: post #71

Some of my results: Desktop Firefox: 25 Desktop Chrome: 26 Laptop Firefox: 16 Laptop Chrome: 20 Laptop Safari: 21 Phone Firefox: 12 Phone Chrome: 10 --- Desktop: 5900X, 3090, Linux Laptop: M1 Pro 14" Phone: S24 Ultra Ran all tests in private window to avoid extensions, and gave a minute to cool between tests. Laptop/phone was plugged in.

M1 MacBook Air:

Safari: 24.1

Firefox: 21.7

Extensions can really slow things down:

Safari w/ Ghostery: 6.83

Safari w/ AdBlock: 13.0

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#87

Post by Lacusch »

kleiba wrote: post #62

By far the biggest speed complaint I have about Firefox is not in everyday use, but whenever I restore a previously saved session - it basically stops reacting for a few minutes(!) before eventually I can use it again. I suppose it's due to the anti-virus interfering with some kind of memory image or whatever but whatever it is, it's so annoying.

I've the same problem on Linux with no antivirus installed

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#88

Post by mdasen »

sedatk wrote: post #79

On my machine, Firefox got 12.3, and Edge (Chromium) got 12.8. I don't believe that the performance characteristics of these two are that close unless I'm missing something. For example, audio players on Edge stutter a lot while Firefox plays them smoothly. An example is: https://deepsid.chordian.net/ I believe Edge is slower not because Chromium is slow, but because of Microsoft's overreaching efforts on energy cons…

Audio wouldn't be going via the DOM or JS, right? I know that Firefox has its own codec support and that Safari on Mac uses different AV stuff than other browsers.

I don't think that AV stuff would be tested by Speedometer.

Re: Speedometer 3.0: A shared browser benchmark for web application responsiveness

#89

Post by freediver »

This collaboration is pretty exciting. I would expect that the teams of all three rendering engines (WebKit, Blink, Gecko) have done whatever they could to improve performance for the launch and that there won't be any outliers at the beginning with all of them having similar performance.

But the title of future performance king is up for grabs! And now we have a de-facto standard for browser performance benchmarking.

Post reply on HN