Edge Performance Profiling missing useful features

By design Issue #7418304


May 2, 2016
This issue is public.
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

In latest Edge developer tool, the performance profiling has added many new features, but also removed some important features (compare to IE 11 developer tool), e.g., many information columns are removed, especially call count.

Can you please add them back?


1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Brad E.”

  • Hello,

    Just so we are clear - could you provide the version of Edge that you are using? This would be helpful in understanding which features you are referring to.

    All the best,
    The MS Edge Team

  • Microsoft Edge Team

    Changed Assigned To from “Brad E.” to “Andy S.”

  • Microsoft Edge 25.10586.0.0

    In Edge F12 Developer Tools -> Performance tab -> JavaScript call stacks tab, it only provide 5 columns:

    • Inclusive CPU (%)
    • Exclusive CPU (%)
    • Inclusive CPU (ms)
    • Exclusive CPU (ms)
    • URL

    Missing following columns that was in IE 11 Developer Tools: (Refer to above attachment (IE11_Profiler.png)

    • Count [very important]
    • Avg time (ms) [very important]
    • Max time (ms)
    • Min time (ms)
    • Function Type
    • Line number
    • Worker Id
  • Microsoft Edge Team

    Changed Status to “By design”

  • Thanks for the feedback! In Edge the profile information is collected via CPU stack sampling. This is a far more accurate way to collect profiling information as it does not introduce overhead into the application. The previous mechanism used to collect data was via instrumentation wherein every single function call triggers an event on entering and exiting the function. The time between those two events is then measured and reported. This overheard can cause some functions being profiled to be a lot more costly then they are which is misleading. Though, one of the benefits with instrumented collection is that every call is measured so call counts can be given which is not true for sampled. I sure appreciate that it’s useful feature especially if you’re using the profiler more as a call flow analysis tool to understand how your application executed. For future releases of Edge we will be considering ways to bring back some of the lost data and to improve the tools or offer alternatives.

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

Sign in