Performance investment: insertBefore and setContext could be faster in Microsoft Edge

Confirmed Issue #7150818 • Assigned to Eugene V.

Details

Author
Kagami R.
Created
Apr 8, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14316
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

  1. Go http://codepen.io/SaschaNaz/pen/RrGaPj
  2. Wait until the test ends.
  3. Check the elapsed time.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Rico M.”

    • I think this is main reason why Edge is much slower on Twitter website than others. Clicking “View 1000+ new Tweets” just makes Edge freeze while Firefox and Chrome finishes loading in a few seconds.

    • edge 37.14316.1000.0 – 223.665
      yandex.browser 16.3.0.7146 – 42.66

    • I saw 12000+ ms on April 8 and now see just 100+ ms. I can’t understand what happened as I used the same build 14316. Anyway, still 5x times slower than others as Chrome and Firefox shows 20+ ms.

    • Microsoft Edge Team

      Changed Assigned To from “Rico M.” to “Todd R.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed”

    • Prior to Edge 14, promises were not executed as microtasks. We recently shipped a flight where we moved promises from timeout scheduler to microtask scheduler. This is likely what caused the 100x improvement.

       

      I’ve just traced this on an internal build MQEDGE 14320 on a Surface Book and saw ~73 ms.

       

      My breakdown is:

      1. CNode.insertBefore is 32 ms

      2. CNode.setContext is 15 ms

      3. CDocument.createElement is 2 ms

      4. Some Chakra or script overhead for ~6-11 ms

      5. Creating promises is ~3 ms

      6. Various other small costs ~10-11 ms

       

      CNode.insertBefore and CNode.setContext are the obvious targets for future optimization. Moving this bug to the DOM team.

    • Microsoft Edge Team

      Changed Title from “Manipulating DOM is 100+ times slower on Edge” to “insertBefore and setContext could be faster in Microsfot Edge”

    • Also the title on this bug is currently inaccurate. Updating title to be more accurate and reflect the current state of this bug.

    • Microsoft Edge Team

      Changed Title from “insertBefore and setContext could be faster in Microsfot Edge” to “insertBefore and setContext could be faster in Microsoft Edge”

      Changed Assigned To to “Travis L.”

      Changed Assigned To from “Travis L.” to “Eugene V.”

      Changed Status to “Confirmed”

      Changed Title from “insertBefore and setContext could be faster in Microsoft Edge” to “Performance investment: insertBefore and setContext could be faster in Microsoft Edge”

    You need to sign in to your Microsoft account to add a comment.

    Sign in