Raptor YouTube playback performance documentation
Categories
(Testing :: Raptor, defect, P1)
Tracking
(firefox69 fixed)
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
(Blocks 1 open bug)
Details
This bug covers the necessary work to get the recently added YouTube playback performance tests documented.
Most likely everything should be added to:
https://wiki.mozilla.org/Performance_sheriffing/Raptor
Rob, where should I document the handling with the external test page? Should it also go into the same page, or shall I create a new sub page for the particular test suite?
Assignee | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
(In reply to Henrik Skupin (:whimboo) [⌚️UTC+2] from comment #0)
This bug covers the necessary work to get the recently added YouTube playback performance tests documented.
Most likely everything should be added to:
https://wiki.mozilla.org/Performance_sheriffing/RaptorRob, where should I document the handling with the external test page? Should it also go into the same page, or shall I create a new sub page for the particular test suite?
I'd suggest adding a section under the benchmark tests list [0] but if you want to create a sub page and just add a link there to it that works for me, thanks!
[0] https://wiki.mozilla.org/Performance_sheriffing/Raptor#Benchmark_Tests_2
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
The following places will contain information about the tests:
Overview: https://wiki.mozilla.org/Performance_sheriffing/Raptor#raptor-youtube-playback
Details: https://wiki.mozilla.org/Performance_sheriffing/Raptor/Youtube_playback_performance
Assignee | ||
Comment 3•5 years ago
|
||
Rob, can you please check the content of those newly added docs? In case something is unclear please let me know.
One question through, where do you want to see the documentation for handling the Performance playback test suite as mirrored at https://github.com/mozilla/perf-youtube-playback/? Should it be in its wiki, or also on the Wiki?
Comment 4•5 years ago
|
||
(In reply to Henrik Skupin (:whimboo) [⌚️UTC+2] from comment #3)
Rob, can you please check the content of those newly added docs? In case something is unclear please let me know.
One question through, where do you want to see the documentation for handling the Performance playback test suite as mirrored at https://github.com/mozilla/perf-youtube-playback/? Should it be in its wiki, or also on the Wiki?
Thanks for the documentation, it looks great (I added the command line for running on GVE). If I'm understanding your question correctly, I think further details about the playback suite itself are fine inside it's own wiki at https://github.com/mozilla/perf-youtube-playback/, since you've linked to there in the Raptor wiki already anyway. Thanks again, the documentation will be very useful.
Assignee | ||
Comment 5•5 years ago
|
||
I added the docs for updating the YouTube test suite:
https://github.com/mozilla/perf-youtube-playback/wiki
If there is something missing please add. Otherwise I call this bug fixed.
Comment 6•5 years ago
|
||
(In reply to Henrik Skupin (:whimboo) [⌚️UTC+2] from comment #5)
I added the docs for updating the YouTube test suite:
https://github.com/mozilla/perf-youtube-playback/wikiIf there is something missing please add. Otherwise I call this bug fixed.
Looks great and very helpful, thanks!
Assignee | ||
Comment 7•5 years ago
|
||
I will leave the needinfo for Dave for a post-check, but mark it as fixed now. Thanks!
Comment 8•5 years ago
|
||
The documentation looks good, thanks Henrik. We should have a contact for all perf tests, and I notice that this doesn't. Do either of you have a suggestion for someone who can help us to understand and investigate regressions for this test? Perhaps someone from the graphics team would be willing to put their name down?
Assignee | ||
Comment 9•5 years ago
|
||
The primary contact should be Arnold and Alexandru, right? Not sure if it makes sense to add media folks here. Based on the regression someone else might be the contact, so maybe leave it up for SV whom to contact?
Comment 10•5 years ago
|
||
If it was a specific developer whom asked to have this particular test put into production then I'd suggest that she/he be the primary contact along with one person from our team - that way we have the developer who may be interested in if the numbers regress, as well as a contact on our team for test/framework breakages. For the other tests I would suggest we do the same if possible.
Description
•