Peter added a comment.
I'll start with this later this week. One thing you can start with is this: > We don't have ongoing measurement of javascript performance so it might get worse without us noticing. You can use the User Timing API <https://developer.mozilla.org/en-US/docs/Web/API/User_Timing_API> for that, that would be super helpful if that is added before its used by real users. If you use the API those metrics are automatically picked up by our synthetic measurement tools if we point them to the query builder. If you feel like it you can create your own synthetic test, you can checkout searchWvuiObama.js in https://github.com/wikimedia/performance-synthetic-monitoring-tests/tree/master/tests/desktop how that can be done (I can also help you). You can also have a look how the team implemented user timings for the Wvui search. You can also beacon those metrics back to your server from real users, that is good so we can pickup if there are some users that struggle with the performance. Could those tag along with the other metrics you are measuring or are those backend only in your graphs? TASK DETAIL https://phabricator.wikimedia.org/T287769 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Peter Cc: dpifke, conny-kawohl_WMDE, karapayneWMDE, Lucas_Werkmeister_WMDE, Michael, Lydia_Pintscher, Krinkle, Aklapper, Ladsgroup, Invadibot, maantietaja, Akuckartz, Nandana, Jony, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Vali.matei, _jensen, rosalieper, Scott_WUaS, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org
