Issue metadata
Sign in to add a comment
|
Improve performance of horrific O(N^2) setsize/posinset computation |
||||||||||||||||||||||
Issue descriptionThe AutoSetSize/AutoPosInSet computations can be extremely slow if there are many siblings. They need to cache information provided before. They are particularly bad as the web page continues to load, because they will continue to compute information for the same DOM nodes over and over. @dmazzoni suggest that this calculation should be done on the browser side, which probably makes sense.
,
Nov 21
@akihiroota, can you take a look at this one?
,
Jan 11
aleventhal@ I recently finished moving PosInSet and SetSize calculations to the browser side and am in the process of deleting AutoPosInSet and AutoSetSize from the codebase. Sorry it took so long to get back to you on this, I am just coming across this now. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by aleventhal@chromium.org
, Apr 9 2018