Loading tweets is much slower than Firefox

Not reproducible Issue #7163905

Details

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

Sign in to watch or report this issue.

Steps to reproduce

  1. Go twitter.com and sign in
  2. Wait until there are 100+ tweets to load
  3. Click ‘View (n>100) new tweets’
  4. Wait until the load finishes
    Screen capture: https://twitter.com/SaschaNaz/status/719158623893454849/photo/1

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Rico M.”

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

      Changed Status to “Confirmed”

    • Broke down a quick trace of 51 tweets on my Surface Book on an internal build MQEDGE 14320 that has slightly newer code than public 14316 build for some DOM APIs which may cause it to be slghtly faster.

       

      There is some room for Microsoft Edge to improve here but not one or two APIs to quickly improve.

       

       Getting new tweets took ~1562 ms in Microsoft Edge and the break down was:

      RegExp-351 ms

      get_innerWidth 334 ms (forced synchronous layout)

      getElementsByClassName 118 ms

      Set_InnertHtml 70 ms

      querySelectorAll 66 ms

      webkitMatchesSelector 46 ms

      HTMLCollection.length 40 ms

      Celement.getAttribute 25 ms

      Cnode.insertBefore 21 ms

      Cnode.appendChild 18 ms

      Celement.get_className 14 ms

      Various HTML Collection Calls-~30-60 ms (Ideally, we need to write up a technique for breaking this down. I found a lot of these while reviewing trace carefully but did not figure out the best technique.)

      Other EdgeHTML APIs ~100-200 ms

      The rest seems spread amongst a lot of Chakra code. ~200-300 ms

       

      Also tested the scenario in Chrome and Firefox and observed that Firefox seems fastest of the three although I did not measure specifics so take that with a grain of salt.

    • Microsoft Edge Team

      Changed Status from “Confirmed”

      Changed Assigned To to “Rico M.”

      Changed Assigned To from “Rico M.” to “Daniel L.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Daniel L.” to “Todd R.”

      Changed Status from “Confirmed” to “Not reproducible”

    • We’ve done additional reviews on newer builds and are only seeing minor variations in the performance of Microsoft Edge when compared to other browsers under most circumstances. 14316 had a significant issue in certain DOM APIs such as setInnerHtml that could have contiributes to the observed perf issue. If you are able to reliably reproduce significantly slower speeds in Microsoft Edge on builds 14342 and newer, please reactivate this bug, gather a trace and submit a zip of it attached to this bug using instructions from https://developer.microsoft.com/en-us/microsoft-edge/platform/documentation/performance-analysis/windows-performance-toolkit/.
      Thanks!
      -Todd

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

    Sign in