Chrome 101

Results for chrome 101 are published: https://krausest.github.io/js-framework-benchmark/2022/table_chrome_101.0.4951.41.html

Please note that for some benchmarks (most notably create 1k and 10k rows) the variance of the measurement increased in comparison to chrome 100. This is rather bad, since ideally we'd like to have low variance since only that guarantees stable results.

(build.zip is experimental. It should allow unzipping in the js-framework-benchmark directory and install the compiled files for all implementations such that building them locally is optional. This note will be updated when I did some further tests.)

Chrome 100

Results for chrome 100 are finally published: https://krausest.github.io/js-framework-benchmark/2022/table_chrome_100.0.4896.127.html

Please note that I had to replace the test runner. The Webdriver benchmark driver returned strange results that could neither be explained nor reproduced for clear rows. Thus I switched to puppeteer. Sadly the variance in the measurement has gone up and numbers appear not to be directly comparable to the older webdriver results such that I'm not publishing the chart showing the performance across chrome versions. See #1020 for the full drama.

(build.zip is experimental. It should allow unzipping in the js-framework-benchmark directory and install the compiled files for all implementations such that building them locally is optional. This note will be updated when I did some further tests.)

Chrome 99

Results for chrome 99 are published: https://krausest.github.io/js-framework-benchmark/2022/table_chrome_99.0.4844.51.html

Looks like no big changea in chrome's performance (maybe except alpine for clear row, which got much faster):

Chrome 98 results

Results for chrome 98 are published: https://krausest.github.io/js-framework-benchmark/2022/table_chrome_98.0.4758.80.html

Here's the chart for vanillajs-keyed for the latest chrome versions: