Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Performance] Investigate and implement userTiming API metrics to a "problematic page" #4401

Closed
2 of 3 tasks
unlikelyzero opened this issue Oct 29, 2021 · 4 comments
Closed
2 of 3 tasks

[Performance] Investigate and implement userTiming API metrics to a "problematic page" #4401

unlikelyzero opened this issue Oct 29, 2021 · 4 comments
Labels
needs:test instructions Missing testing notes performance impacts or improves performance type:enhancement

Comments

@unlikelyzero
Copy link
Collaborator

unlikelyzero commented Oct 29, 2021 •
edited

Is your feature request related to a problem? Please describe.
We should understand and implement UX Centric performance measurements for problematic parts of the application. A great first implementation would be the time it takes a plot to render on a Display Layouts

Describe the solution you'd like

  • Investigate the userTiming API
  • Present to team
  • Implement a single timing metric on a problematic page like Display Layouts

Additional context
https://github.com/ux-capture/ux-capture is a wrapper for the existing API
@unlikelyzero unlikelyzero added type:enhancement performance impacts or improves performance labels Oct 29, 2021
@unlikelyzero unlikelyzero mentioned this issue Apr 1, 2022
Merged
15 tasks
@shefalijoshi
Copy link
Contributor

Please add testing instructions.

@khalidadil
Copy link
Contributor

@unlikelyzero Is this just adding the performance mark to the View Large? What work was done under this issue?

@akhenry akhenry added the needs:test instructions Missing testing notes label Apr 25, 2022
@unlikelyzero
Copy link
Collaborator Author

@shefalijoshi this landed in 2.0.3 and will need to be retested at some point in the future

@unlikelyzero unlikelyzero reopened this Jun 9, 2022
@unlikelyzero
Copy link
Collaborator Author

Will consider this closed as a part of yesterday's testathon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs:test instructions Missing testing notes performance impacts or improves performance type:enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@khalidadil @akhenry @shefalijoshi @jvigliotta @unlikelyzero