syduki

> so is that good or bad 😆 it depends, for benchmark purposes it is a clever cheat, for real-world applications it is an awful feature/behavior.

Very exciting "issue" indeed :smile:. But seriously, this should have happened soon or later, it is doubtful a Chrome 124 issue. It is naive at least to expect benchmark consistency...

@krausest Well, I can just admit that we have very different perception of benchmark consistency. Here, I consider consistency to be relevant in a narrow field only, depending on specific...

> Also, in my opinion, node creation speed isn't that important that needs a ~60% weight, but content updating speed affects user experience in a bigger aspect. While I am...

> people take this benchmark as gold standard That was a strong saying. To my knoweledge the [reality](https://survey.stackoverflow.co/2023/#web-frameworks-and-technologies) is far away from that. I personally didn't saw so such evidence...

Indeed, that's for _developers_, or if parroting your words - the _people_. A _developer_ is always an _user_ of some piece of technology, as JS in this very case, and...

It would be hard to spot this just by looking at the code, most probably it would require some debug output here and there to narrow it down. But from...

Those 1 & 2 were too optimistic, from your capture looks it is a worse case, more likely tied to CDP itself. Let's see if it improves with the webdriver.

You can try some more things: 1. Inline `appendRows` function. The reason behind this is that `ivi` is doing a lot of inlining so theoretically it could get some optimization...