Chrome 111

Results for Chrome 111 are published: https://krausest.github.io/js-framework-benchmark/2023/table_chrome_111.0.5563.64.html

Looks very similar to Chrome 110.

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 110

Results for Chrome 110 are published: https://krausest.github.io/js-framework-benchmark/2023/table_chrome_110.0.5481.77.html

Seems like Chrome 110 is fast again. It's about 10% faster for create rows than Chrome 109 and comparable to Chrome 108 again.

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 109

Results for Chrome 109 are published: https://krausest.github.io/js-framework-benchmark/2023/table_chrome_109.0.5414.87.html

Seems like Chrome 109 is about 10% slower slower for create rows than Chrome 108 (42.6 msecs instead of 38.9).

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 108

Chrome 108 results are available: https://krausest.github.io/js-framework-benchmark/2022/table_chrome_108.0.5359.71.html

No big changes in this release as far as this benchmark is concerned.

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 107

Chrome 107 results with puppeteer are available: https://krausest.github.io/js-framework-benchmark/2022/table_chrome_107.0.5304.62.html

No big changed, though it's interesting that puppeteer reports a lower memory usage (pretty much constantly ~300kb less).

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 106

Results for chrome 106 are in. Didn't see anything real exciting about those.
Please note that the remove row benchmark now uses 4x CPU throttling.

https://krausest.github.io/js-framework-benchmark/2022/table_chrome_106.0.5249.61.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)

Chrome 105

Results are updated for chrome 105:
https://krausest.github.io/js-framework-benchmark/2022/table_chrome_105.0.5195.102.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)

Discussion:
Looks like no big changes. Seems like the remove row benchmark got worse for a few fast frameworks like e.g. solid, wasm- bindgen and blockdom. Maybe we'll add a CPU slowdown for the remove benchmark in the next run.
Select row has already a really high CPU slowdown and we should observe whether the values are still meaningful (1more and blockdom were a bit slower than the other fast frameworks for chrome 104 too).

Chrome 104

Results for chrome 104 are in: https://krausest.github.io/js-framework-benchmark/2022/table_chrome_104.0.5112.79.html
Once again on my MacBook Air M1. I used puppeteer for this run, playwright reported a bit strange results for remove row.

Chrome 103

Results for chrome 103 are ready: https://krausest.github.io/js-framework-benchmark/2022/table_chrome_103.0.5060.53_osx.html
This time I wanted to use my MacBook Air. I decided to use a cloud vm to build the frameworks. This was a bit more work than I thought.
I switched to latest node tls (v16.15.1). Running npm ci caused an update of most lock files and was incredibly slow, so I decided to npm install all frameworks which broke quite a few of them.
As a target platform to build and host the frameworks I decided to play with a virtual cloud server. So far the framework information (e.g. version) was loaded from the disk, and only the assembled files were loaded over http. I switched from lws to an express server that also provides the framework information. npm start starts this server now.
Overall I'm not happy with the large standard error in the create 1,000 rows benchmark. Maybe I find the time to check linux results (though the days of my linux laptop are mostly gone).

As usual the attached zip file contains all precompiled frameworks. Just unzip in the js-framework-benchmark root dir, start the web server npm start and start running the benchmark npm run bench

Chrome 102

Results for chrome 102 are published: https://krausest.github.io/js-framework-benchmark/2022/table_chrome_102.0.5005.61.html

Attached is a zip file with all precompiled frameworks. Just unzip in the js-framework-benchmark root dir, start the web server npm start and start running the benchmark npm run bench
build.zip