Live data from Hacker News

Speedometer 3.0: A shared browser benchmark for web application responsiveness

browserbench.org

111–120 of 183 posts

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

#111

Earlier quoted context omitted.

The score goes from 0 to 140 so that there's some room for when the computers will get faster. When we started working on this, all browsers were maxed at 140, so the computation got changed.

I thought the front page goes to 140 just because it is modeled after actual GM dashboard speedometers produced ~1960-1990, sometimes having range 0-85 MPH, or 0-140km/h in metric markets.

Yes.

The speedometer graphic was inherited from Speedometer 2. When Speedometer 2 was released, scores were in a reasonable car-speed range. The combination of hardware and software improvements meant that early versions of Speedometer 3 (which includes a subset of Speedometer 2 tests) were consistently scoring above 140, so we adjusted the scaling factor (IIRC, by ~20x) to give plenty of room for future improvements.

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

#112

In descending order.... MacBook Pro, M2 Pro, 16GB, plugged in, external display: Safari=31.2 Chrome=29.4 iPhone 12 mini, plugged in: Safari=19.4 HP Z2 mini (i7): Edge=15.9 Panasonic Toughbook CF19 (win 10): Edge=4.7 Chrome=5.6 Galaxy Tab S5e: Chrome=2.2 Oculus Quest 2: browser crashed Tizen TV: displayed, wouldn't run Nintendo 2DS: displayed, no css, wouldn't run

[deleted]

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

#113

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.

[deleted]

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

#114
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…

[deleted]

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

#115
post #93

I 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…

[deleted]

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

#118
post #88
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.

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

It probably isn't, but fwiw yes web audio is controlled by JavaScript. Doing it right means using web audio worklets, which is a special purpose JS context that has no access to your main page context.

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

#119

Got "Infinity" after testing my Firefox Dev Edition 123b9. Is this because of my FF config because my browser is perhaps blocking something (e.g. canvas, fingerprint, etc) or any result north of 140 is considered infinity?

Do you see anything (errors or something else) in the web console?

I also got Infinity, on Firefox 123.0.1, with a bunch of privacy extensions.

There is only one warning in the Console: Ignoring ‘preventDefault()’ call on event of type ‘wheel’ from a listener registered as ‘passive’. react-dom.production.min.js:29:112

Post reply on HN