Chrome 132 results

Results for chrome 132 are published.

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

The run was a little bumpy due to several things:

• total duration for the benchmark is just pretty long. This together with the varying results for each run (see #1721) makes it hard to publish official results. I changed the order of the benchmark such that the outer loop iterates over the benchmarks and the inner over all frameworks. This way I hope to be able to interrupt a benchmark run and continue from that benchmark. Results should be pretty okay, as long as the full benchmark is repeated for all frameworks.
• It took three runs to get complete results: CPU results for keyed in the first night, all benchmarks for non-keyed in the second night and memory and startup for keyed the third day
• There was an error for non-keyed/skruv-liten such that I had to run that seperately after the benchmarks
• Just before publishing the results we found one framework that performs the event logic in the pointerup event and thus before the click event. Thus we didn't count the full duration for that framework. We've added some code to allow selecting which event starts the measurement in the package.json.
• This was the first run on my new MacBook M4 Pro such that it can't be compared with earlier chrome results. Maybe the bigger number of performance cores helps with #1721.

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 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)