Get more performance insights
We need to get more information on the framework overall performance, possible memory leaks and other malfunctions.
Usage of about:performance
and about:memory
can help on Firefox.
Need to study:
- https://developer.mozilla.org/en-US/docs/Web/API/Window/performance
- https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming
- https://developer.mozilla.org/en-US/docs/Web/API/User_Timing_API
- https://stackoverflow.com/questions/15970525/how-to-find-js-memory-leaks
- https://developers.google.com/web/tools/chrome-devtools/memory-problems
- https://web.dev/rail/
So that we stop ending up with users consuming 750MB of RAM for hubl or any of our applications and get ideas on how to improve our codebase.
Need to implement some tests scenarios after studying the links above.
Need to test explicitely our applications like Hubl and Coopedia.
And the perfect tool Firefox released for that is : https://profiler.firefox.com/
You can share performance capture with other team members here, just by capturing it on your side using the dev tools, saving it as JSON and then loading it there. Perfect tool.
Also gives you a complete overview of the load associated with each function you're executing. See the screenshot for reference: