Chrome 132 results

[krausest]

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 Incremental runs are worse than full runs #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 Incremental runs are worse than full runs #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)

---

This discussion was created from the release Chrome 132 results.