Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-25414

Identify relevant key performance metrics and measurements

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.3
    • Component/s: Web UI
    • Release Notes Summary:
      Added key metrics to track performance
    • Release Notes Description:
      Hide

      As relevant metrics we identified those already collected by the devtools of most browsers:

      Additionally, we’re including an experimental set of network metrics, which take all requests performed by the browser into account to compute:

      However, some requests seem to be ignored and not included in the performance entries (https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntries) on Chrome, which renders this data incomplete in this browser. Furthermore, transfer size and decoded body size cannot be retrieved on Safari and Edge.

      We are also storing a set of custom performance marks and measurements, which are aligned with what we want to measure:

      • [mark] nuxeo-app.ready: marks the moment when the nuxeo-app element is ready
      • [mark] nuxeo-app.page-changed: marks the last moment where there was a page switch (not set when the first page is loaded, since there is not transition)
      • [mark] nuxeo-app.page-loaded: marks the moment where the last dom-change event was fired from within the current page, .i.e, the last moment in which there were changes in the page
      • [measurement] <page-name>.dom-changed: a measurement between the moment in which the last dom-change event is fired from within the current page and the last page-change mark (or PerformanceTiming.fetchStart if undefined) - this is mostly helpful for development and debugging purposes

      We added these metrics to the performance analyzer added in NXP-25303. You can try these out by running:

      Nuxeo.Performance.report({networkStats: true});
      
      Show
      As relevant metrics we identified those already collected by the devtools of most browsers: dom content loaded first contentful paint first pain on load Additionally, we’re including an experimental set of network metrics, which take all requests performed by the browser into account to compute: finish time: time taken to complete all requests since PerformanceTiming.fetchStart request count: the number of requests issued transfer size decoded body size However, some requests seem to be ignored and not included in the performance entries ( https://developer.mozilla.org/en-US/docs/Web/API/Performance/getEntries ) on Chrome, which renders this data incomplete in this browser. Furthermore, transfer size and decoded body size cannot be retrieved on Safari and Edge. We are also storing a set of custom performance marks and measurements, which are aligned with what we want to measure: [mark] nuxeo-app.ready : marks the moment when the nuxeo-app element is ready [mark] nuxeo-app.page-changed : marks the last moment where there was a page switch (not set when the first page is loaded, since there is not transition) [mark] nuxeo-app.page-loaded : marks the moment where the last dom-change event was fired from within the current page, .i.e, the last moment in which there were changes in the page [measurement] <page-name>.dom-changed : a measurement between the moment in which the last dom-change event is fired from within the current page and the last page-change mark (or PerformanceTiming.fetchStart if undefined ) - this is mostly helpful for development and debugging purposes We added these metrics to the performance analyzer added in NXP-25303 . You can try these out by running: Nuxeo.Performance.report({networkStats: true });
    • Sprint:
      nxGang Sprint 10.2.9, nxGang Sprint 10.3.1
    • Story Points:
      2

      Description

      Identify relevant key metrics and measurements to track performance issues in Web UI

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 days, 3 hours
                  3d 3h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.