Chrome 133 results

[krausest]

I just saw that I already grumbled that the chrome 132 run wasn't straight forward. Obviously I didn't know what expected me for chrome 133 😄 .

Some time ago I decided to switch to the chrome for testing (https://github.com/GoogleChromeLabs/chrome-for-testing#json-api-endpoints). I hoped incremental runs were better if I used a fixed chrome version without the security updates. However as it turned out there appears to be an issue with the chrome traces for chrome for testing (#1838 ). A solution would have been to restart the chrome process for each and every benchmark loop. However this creates such noisy results that make no sense to publish (and the whole benchmark run takes too long then).

Luckily the issue does not happen for the normal chrome edition. So we're back to that and I'm absolutely happy to publish the results for chrome 133: https://krausest.github.io/js-framework-benchmark/index.html

Other than that I didn't see big changes.

---

This discussion was created from the release Chrome 133 results.

[leeoniya]

nice. is this the first time we've seen a 1.00 baseline? ❤️

that feels like some kind of milestone :)

[krausest]

Yeah - or just the lucky result of a random experiment 😄
But it even happened a second time for the last PRs.
Maybe rebooting, turning mdutil off, quitting all (background) apps, restricting spotlight from indexing most directories and stopping wifi before performing a run helps. We'll see.

[leeoniya]

those tolerances look really tight; it's amazing you're able to pull that off.