- From: Pawel Kozlowski <notifications@github.com>
- Date: Wed, 26 Jul 2017 12:58:35 +0000 (UTC)
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 26 July 2017 12:58:59 UTC
> I think the performance statistics are a good argument for filing a bug on various browsers. Please do so, if you can! @domenic are you saying that people should file perf-related issues if different ways of clearing child nodes perform differently (ex. removeChild in a loop slower as compared to using innerText)? Or just file bugs if we have numbers that _suggest_ removal being slow? I'm asking since in a test / benchark app I'm using removal of _all_ (~1500) nodes take almost 1/2 time needed to create and attach those nodes in JS (~10ms to create nodes vs. ~4ms to delete them). It _seems_ a lot but without having one "blessed" method of clearing children nodes and without knowing underlying implementation details it is hard to draw any conclussions that would justify opening issues on browsers side.... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/478#issuecomment-318045380
Received on Wednesday, 26 July 2017 12:58:59 UTC