4 ms·

See also https://arewefastyet.com https://arewefastyet.com.

by e4m2 3y ago

flerchin 3y ago
Really cool how you can see Firefox speed enhancements showing up in discrete steps. I am surprised to see Chrome faster than Chromium. What is google doing in their branded flavor?
- kirbyfan64sos 3y ago
  Chrome tends to be built with a rather slow and stringent set of optimization extras like PGO that people tend to leave off in Chromium builds.
- lillecarl 3y ago
  On windows you can speed chromium up by renaming it to chrome.exe so it gets special treatment by antivirus software.
  - lolinder 3y ago
    That's incredibly dumb if true, but can't be the whole story because the difference is still present in the Linux stats.
  - voxic11 3y ago
    Doesn't windows check the signature or something to decide if an application should be allowed to bypass antivirus? Seems like doing it based on the filename would be a pretty huge security hole.
  - tredre3 3y ago
    Chromium's executable[1][2] is already named chrome.exe unless the builder goes out of their way to rename it. This can't be the reason. 1. https://download-chromium.appspot.com/ https://download-chromium.appspot.com/ 2. https://ungoogled-software.github.io/ungoogled-chromium-binaries/releases/windows/ https://ungoogled-software.github.io/ungoogled-chromium-bina...
- ttarr 3y ago
  Probably PGO. Even prebuilt Firefox tend to be faster than distro provided ones, at least at some point on the past.
  - kurtoid 3y ago
    Looks like the Arch repos do PGO on firefox: https://gitlab.archlinux.org/archlinux/packaging/packages/firefox/-/blob/main/PKGBUILD#L166 https://gitlab.archlinux.org/archlinux/packaging/packages/fi...
toastal 3y ago
I believe this domain started at the big 4.x version drop which was the turn of a new era in the Browser Wars. I remember using Minefield because the new features were too tempting to miss & this was before evergreen versioning became the norm.
deleted 3y ago
[deleted]
dumpster_fire 3y ago
I'd prefer if they kept the y-axis starting at zero for a more realistic representation.
austin-cheney 3y ago
As a JavaScript developer my priorities are limited to visual render and DOM access. Going back 5+ years ago Chrome was able to access the DOM at about 45m ops/s on my desktop and Firefox was achieving about 850m ops/s on the same hardware. On my laptop (faster memory) Chrome was getting up to 55m ops/s while Firefox was around 1.4b ops/s. Now Firefox numbers have remained constant, but Chrome struggles to hit 20m ops/s in my desktop. Chrome has sacrificed front end performance across the board for modest performance improvements to query string access of the DOM. Pretty unfortunate.
- kstrauser 3y ago
  How many cores was laptop benchmark running on?
  - austin-cheney 3y ago
    I believe the CPU is 4 core, JavaScript is single threaded (multi-callstack) so you only get 1 logical CPU core.
    - kstrauser 3y ago
      I thought so, but wasn't sure. That makes me super suspicious of 1.4B op/s. Surely Firefox isn't accessing the DOM in ~2 CPU cycles?
      - austin-cheney 3y ago
        Appears to be: https://jsbench.github.io/#b39045cacae8d8c4a3ec044e538533dc https://jsbench.github.io/#b39045cacae8d8c4a3ec044e538533dc Its just a crude memory operation for Firefox. The video card in my laptop is super inferior compared to my desktop, so in most other benchmarks the laptop is much slower. The laptop has DDR4 memory where the desktop has slower DDR3 memory.
- magicalist 3y ago
  "access the DOM" is not a constant operation, though, it will vary wildly based on what you're doing and what you were doing just before that (think of reading a computed style before vs after writing a style that forces layout). 1.4b ops/s also sounds like it might not be testing what you think it's testing. Access in that case might just be hitting a cache, so possibly not at all representative of real performance of a web app.
Nezteb 3y ago
Also https://awsy.netlify.com/ https://awsy.netlify.com/!
moffkalast 3y ago
Hey they forgot to include the WebGPU speed comparison... oh wait ;)

See also https://arewefastyet.com https://arewefastyet.com.

by e4m2 3y ago

See also https://arewefastyet.com https://arewefastyet.com.

Really cool how you can see Firefox speed enhancements showing up in discrete steps. I am surprised to see Chrome faster than Chromium. What is google doing in their branded flavor?

kirbyfan64sos 3y ago
Chrome tends to be built with a rather slow and stringent set of optimization extras like PGO that people tend to leave off in Chromium builds.
lillecarl 3y ago
On windows you can speed chromium up by renaming it to chrome.exe so it gets special treatment by antivirus software.
- lolinder 3y ago
  That's incredibly dumb if true, but can't be the whole story because the difference is still present in the Linux stats.
- voxic11 3y ago
  Doesn't windows check the signature or something to decide if an application should be allowed to bypass antivirus? Seems like doing it based on the filename would be a pretty huge security hole.
- tredre3 3y ago
  Chromium's executable[1][2] is already named chrome.exe unless the builder goes out of their way to rename it. This can't be the reason. 1. https://download-chromium.appspot.com/ https://download-chromium.appspot.com/ 2. https://ungoogled-software.github.io/ungoogled-chromium-binaries/releases/windows/ https://ungoogled-software.github.io/ungoogled-chromium-bina...
ttarr 3y ago
Probably PGO. Even prebuilt Firefox tend to be faster than distro provided ones, at least at some point on the past.
- kurtoid 3y ago
  Looks like the Arch repos do PGO on firefox: https://gitlab.archlinux.org/archlinux/packaging/packages/firefox/-/blob/main/PKGBUILD#L166 https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

toastal 3y ago

I believe this domain started at the big 4.x version drop which was the turn of a new era in the Browser Wars. I remember using Minefield because the new features were too tempting to miss & this was before evergreen versioning became the norm.

deleted 3y ago

[deleted]

dumpster_fire 3y ago

I'd prefer if they kept the y-axis starting at zero for a more realistic representation.

austin-cheney 3y ago

As a JavaScript developer my priorities are limited to visual render and DOM access. Going back 5+ years ago Chrome was able to access the DOM at about 45m ops/s on my desktop and Firefox was achieving about 850m ops/s on the same hardware. On my laptop (faster memory) Chrome was getting up to 55m ops/s while Firefox was around 1.4b ops/s. Now Firefox numbers have remained constant, but Chrome struggles to hit 20m ops/s in my desktop. Chrome has sacrificed front end performance across the board for modest performance improvements to query string access of the DOM. Pretty unfortunate.

kstrauser 3y ago
How many cores was laptop benchmark running on?
- austin-cheney 3y ago
  I believe the CPU is 4 core, JavaScript is single threaded (multi-callstack) so you only get 1 logical CPU core.
  - kstrauser 3y ago
    I thought so, but wasn't sure. That makes me super suspicious of 1.4B op/s. Surely Firefox isn't accessing the DOM in ~2 CPU cycles?
    - austin-cheney 3y ago
      Appears to be: https://jsbench.github.io/#b39045cacae8d8c4a3ec044e538533dc https://jsbench.github.io/#b39045cacae8d8c4a3ec044e538533dc Its just a crude memory operation for Firefox. The video card in my laptop is super inferior compared to my desktop, so in most other benchmarks the laptop is much slower. The laptop has DDR4 memory where the desktop has slower DDR3 memory.
magicalist 3y ago
"access the DOM" is not a constant operation, though, it will vary wildly based on what you're doing and what you were doing just before that (think of reading a computed style before vs after writing a style that forces layout). 1.4b ops/s also sounds like it might not be testing what you think it's testing. Access in that case might just be hitting a cache, so possibly not at all representative of real performance of a web app.

Nezteb 3y ago

Also https://awsy.netlify.com/ https://awsy.netlify.com/!

moffkalast 3y ago

Hey they forgot to include the WebGPU speed comparison... oh wait ;)