Releases: krausest/js-framework-benchmark
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!
Chrome 121
Chrome 121 are published: https://krausest.github.io/js-framework-benchmark/2024/table_chrome_121.0.6167.85.html
This time (but it'll be only this time) I also ran the benchmark on my old windows machine:
https://krausest.github.io/js-framework-benchmark/2024/table_chrome_121.0.6167.86_win.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)
No big changes from chrome 120.
Chrome 120
Chrome 120 results are published.
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)
There's a new view for compressed and uncompressed transfer size and the first paint metric. I'm planning to remove lighthouse metrics so please post in #1492 if you want me to keep it.
The standard view shows the total duration for each benchmark (i.e. including javascript/wasm and rendering duration). There's a new JS only view that shows script duration only and a paint duration only mode. Both are still experimental please post feedback to #1233
The append to table benchmarks changed a bit in this benchmark: It includes now warmup runs.
Chrome 119
Chrome 119 results are published.
Overall results appear to be comparable with chrome 118. Notable exceptions are:
- blazor got faster with chrome 119 (but still one of the slowest)
- react redux got slower (we saw that in #1469) already.
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)
Some frameworks were archived after the chrome 118 run, in case you're missing some implementation.
Since chrome 118 we're now using a weighted geometric mean for the overall result
The number of runs for the CPU benchmarks was bumped from 10 to 15 for all benchmarks except select row, which was bumped to 25 runs. We hope this improves accuracy of the benchmarks
Chrome 118
Chrome 118 results are published.
Please note that there have been significant changes for this run:
- We're now using a weighted geometric mean for the overall result
- The number of runs for the CPU benchmarks was bumped from 10 to 15 for all benchmarks except select row, which was bumped to 25 runs. We hope this improves accuracy of the benchmarks
So please don't hesitate to post in the discussion sections if you find something suspicious.
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)