appendChild is 2x slower than Safari |
||||
Issue descriptionIt's interesting that our appendChild() is very similar to our append() in performance, even though append() is doing fundamentally more work by inserting everything into a document fragment first, and then removing it from the fragment to insert it into the tree. That's very suspicious... where is the inefficiency in our system? The attached benchmark: Safari 10.0.3: appendChild 1.1999999999999993 append 2.6000000000000014 Chrome Canary 59.0.3045.0: appendChild 2.539999999999999 append 2.460000000000001 (This is on my 2012 Retina MBP.)
,
Apr 18 2017
jbroman@, could you take a look?
,
Sep 13 2017
,
Nov 3 2017
,
Mar 21 2018
On my 2013 Trash Can Mac Pro: Google Chrome 65.0.3325.162 (Official Build) (64-bit) Revision 5d04e9e9c8ce31bee0923a8c326a7e9e19c492a3-refs/branch-heads/3325@{#695} appendChild 3.100000089034438 append 2.199999988079071 Safari Version 11.0.3 (13604.5.6) appendChild 1 append 2 (Safari has low res timer stuff so it's not the most precise time, but it still seems they're much faster.) |
||||
►
Sign in to add a comment |
||||
Comment 1 by esprehn@chromium.org
, Mar 25 2017