Sebastiaan Meijerink

My feedback

  1. 147 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    35 comments  ·  Azure portal » Other  ·  Flag idea as inappropriate…  ·  Admin →

    Hey,

    This is something we’re still actively working on. It has a been a big area of investment and it still is moving forward. We keep investing in performance, both from a client and server side perspective.

    We have a few things coming in the near future which should help address some of the initial UI performance issues. We’re also heavily engaged with all of our partners driving a broad effort to improve performance across the portal for all experiences.

    If you have any specific areas which are causing pain please feel free to reach out to me or comment and state if we can contact you, it would be great to understand the common pain points.

    Cheers,
    Sean.

    Sebastiaan Meijerink commented  · 

    Really bad perfomance;

    I get errors like these in the console;

    ekwsk7u9zHr-.js:5 [fx] 4:44:15 PM MsPortalFx.Base.Diagnostics.ErrorReporter 1 MsPortalFx.Base.Diagnostics.ErrorReporter: code: ETIMEDOUT
    message: requestAnimationFrameQ timout after 5 seconds: callback:function(n){var t;return r.pageNavigator?t=r._updatePageViewport(n):r.demandLoadNavigator&&(t=r._updateDemandLoadViewport(n)),t&&(t=t.catchError(d,(function(){}))),t}
    stack: Error: requestAnimationFrameQ timout after 5 seconds: callback:function(n){var t;return r.pageNavigator?t=r._updatePageViewport(n):r.demandLoadNavigator&&(t=r._updateDemandLoadViewport(n)),t&&(t=t.catchError(d,(function(){}))),t}
    at https://portal.azure.com/Content/Dynamic/AqrjeMdkBoDV.js:27:12919

    Sebastiaan Meijerink supported this idea  · 

Feedback and Knowledge Base