Stefan Krause

Chrome issue report is here: https://issues.chromium.org/issues/337900449

@titoBouzout I tried that before, but didn't keep the result. Anyways I repeated the run. It looks like that without sleep: Just as bad as chrome 124 @localvoid Any idea...

@syduki I don't agree at all. I didn't expect chrome to perform equally across versions (and that wasn't the case in the past). But when performance changes between versions there...

I'm really stuck because I have no confidence in the chrome 124+ results, but I have a proposal to resolve that: If we achieve to create a new vanillajs implementation...

Thanks to you (especially @robbiespeed) we found something: The GC didn't work properly for ivi. Tweaking the GC calls made results much more as expected. I uploaded new results for...

One last check. It's really crazy. Forcing GC should help most frameworks, since it prevents GC during execution of the framework. Except that it doesn't help ivi... Duration in msecs...

I'm sorry, all PRs are currently blocked by https://github.com/krausest/js-framework-benchmark/issues/1655

Thanks - I hope to publish results for the PR tomorrow.

[Results](https://krausest.github.io/js-framework-benchmark/current.html) are updated. Nice!

(Sorry, my free time is currently a bit limited, so I can't put as much effort into this as I'd like to do). 1. consistently interactive is the "interactive" audit...