[WICG/webcomponents] Should browsers do bookkeeping on DOM parts after initial parse? (Issue #1030)

See preliminary benchmark in https://playcode.io/1595899 using chrome-dev with experimental platform features on.

My numbers appear to be

cloning
8.100000023841858
getParts
1.5000000447034836
accessNodes
1.0999999791383743
operations
1.800000011920929
replaceChildren
30.5

As you can see, there is huge overhead in replaceChildren, presumably to do bookkeeping on keeping the parts up to date. Given how we expect users to use DOM parts in frameworks, we should think about whether bookkeeping is necesary in v1.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1030
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1030@github.com>