Update cample to v3.2.1-beta.0 #1712
Conversation
|
I don't see any more relevant ways to solve the speed problem without touching the underlying data. If you come into contact with the data, you still need to iterate through all the nodes up to the node you clicked on, and then stop. I tried this option, but the result is about the same as it was. Only a little better by 0.1. |
|
The results are updated (left updated keyed results, right old results). I guess we must take a look at the big picture in the next full run. |
|
@krausest Since the last release, I haven’t changed almost anything in other benchmarks, although the speed has dropped significantly. I don't know what the reason is. Well, this is a one-off launch, so that's ok. The main thing is that now select row shows quick results! |
|
Everything is green - finally. Then only apply graphomaniac changes like changing classList to className, textContent to nodeValue, etc. |
|
@krausest Anyway, thank you very much! I'm just glad that select row was fixed properly! |
|
Everything is green. How beautiful! |
I solved the problem with the click without resorting to the methods described here. The main idea is a stack of real UI, where I store state that is not in contact with the main data. That is, this can be compared to how if we entered some data into the "input", and so this data is, as it were, reflected in this idea.
I don't know, maybe this is a trivial idea, but it sounds interesting to create a separate stack for each DOM element.