Profile load times

[bedeho]

Background

There are quite a lot of screens on Atlas which take time to load, even apart from the latency of video playback. Having a lower loading time is something that would be very valuable for the user experience to be better for consumers, and the first step in that direction is to try to account for what factors contribute to the overall latency. Based on this information one would be in a better position to plan and triage enhancements based on a full ROI evaluation.

Proposal

Identify key screens, including loading the full app itself, and identify how much different factors are contributing to the total latency itself. Factors include everything involved in loading, including

• downloading static assets
• rendering page
• fetching static assets
• fetching data from QN, Orion, etc.

and probably more.

Note

I'm replacing https://github.com/Joystream/atlas/issues/3100, as Atlas is not really the right target for trying to understand scale, that should be each infrastructure piece itself being benchmarked for this purposefully.

[dmtrjsg]

Research and scoping if possible to define priority against YPP release on the Ephesus call when other workstreams duration is planned.