Chrome 131 results

Results for chrome 131 are published.

We're using Chrome for Testing 131.0.6778.85.html for this run and it seems to be a pretty boring result regarding this benchmark.

Attached you find a binary build of all frameworks such that you can run the benchmark without installing and building all frameworks (see README for how to use the build.zip)

Chrome 130 results

Results for chrome 130 are published.

We're using Chrome for Testing 130.0.6723.58 for this run.
Seems like no big changes for this benchmark.

Attached you find a binary build of all frameworks such that you can run the benchmark without installing and building all frameworks (see README for how to use the build.zip)

Chrome 129 results

Results for chrome 129 are published.

We're using Chrome for Testing 129.0.6668.58 for this run.

Attached you find a binary build of all frameworks such that you can run the benchmark without installing and building all frameworks (see README for how to use the build.zip)

Chrome 128 results

Results for chrome 128 are published. Very close to chrome 127, except for first paint. It might be safer to interpret this first paint metric with some caution.

We're using Chrome for Testing 128.0.6613.86 for this run.

Attached you find a binary build of all frameworks such that you can run the benchmark without installing and building all frameworks (see README for how to use the build.zip)

Chrome 127 results

Results for chrome 127 are published. Once again it looks a bit faster than chrome 126!

There a still a lot of alternative vanillajs versions in this run. Cleaning up is still on the TODO list.

We're using Chrome for Testing 127.0.6533.72 for this run.

Attached you find a binary build of all frameworks such that you can run the benchmark without installing and building all frameworks (see README for how to use the build.zip)

Chrome 126 results

Results for chrome 126 are published. Looks faster than chrome 125!

There a still a lot of alternative vanillajs versions in this run. Cleaning up is still on the TODO list.

We're using Chrome for Testing 126.0.6478.55 for this run.

Attached you find a binary build of all frameworks such that you can run the benchmark without installing and building all frameworks (see README for how to use the build.zip)

Chrome 125 results

Results for chrome 125 are published. I'm happy to report that it was much smoother than chrome 124.

There a a lot of alternative vanillajs versions in this run. I promise to clean up but that'll happen later 😄

We're using Chrome for Testing 125.0.6422.60 for this run.

Attached you find a binary build of all frameworks such that you can run the benchmark without installing and building all frameworks (see README for how to use the build.zip)

Chrome 124

I'm really happy to publish results for chrome 124. Actually I didn't believe in getting #1655 fixed, but thanks to @robbiespeed we found the cause.
If you want some details: Seems like window.gc() doesn't clean up all the dom nodes in every case for chrome 124 and somehow those frameworks gained some speed from that (ivi was one of those).
We're using Chrome for Testing from this release on such that we don't have the performance impact of security fixes.

Furthermore we optimized the vanillajs implementations and @syduki added a new vanillajs implementation.

Attached you find a binary build of all frameworks such that you can run the benchmark without installing and building all frameworks (see README for how to use the build.zip)

Chrome 123

Chrome 123 results are published.

Chrome 123 release notes didn't sound too exciting and the non-existing difference between 122 and 123 results confirms that impression.

The result table has been overhauled and looks nicer (thanks @nakrovati)

Attached you find a binary build of all frameworks such that you can run the benchmark without installing and building all frameworks (see README for how to use the build.zip)

Chrome 122

Chrome 122 are available: https://krausest.github.io/js-framework-benchmark/2024/table_chrome_122.0.6261.69.html

Attached you find a binary build of all frameworks such that you can run the benchmark without installing and building all frameworks (see README for how to use the build.zip)

Looks like Chrome 122 is a pretty good release. All benchmarks are a bit faster than on chrome 121!