Open Bug 1553483 Opened 6 years ago Updated 12 hours ago

Investigate how to cache sources and media files of raptor-youtube-playback benchmark

Categories

(Testing :: Raptor, defect, P5)

defect

Tracking

(Not tracked)

REOPENED

People

(Reporter: whimboo, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxp])

Right now the tests are run with use_live_sites set to true, given that the media files are simply too large for us (~14GB) to cache them via mitmproxy in tooltool.

It means that all the files are hosted at https://yttest.prod.mozaws.net/2019/main.html?test_type=playbackperf-test (bug 1548062), and files will be fetched from a Github repository (bug 1553395) in a scheduled interval.

Ultimately we want to get rid of the live site mode, and cache all of them like for any other test via mitmproxy and tooltool.

This bug exists to investigate what's necessary to do.

Note that all the media files are complete movies even only the first 15s are getting played. As such trimming the files could save us a lot of space. But as raised by Eric in one of our streaming test meetings, it might also be valuable to explore if we want to have our own media files.

Priority: -- → P2
Priority: P2 → P3
No longer blocks: 1552738
Severity: normal → S3
Summary: Investigate how to cache sources and media files of raptor-youtube-playback benchmark via mitmproxy and tooltool → Investigate how to cache sources and media files of raptor-youtube-playback benchmark
Whiteboard: [fxp]

Closing this as WONTFIX as discussed during the Triage meeting, since caching the media files would defeat the purpose of having tests for live sites.

Status: NEW → RESOLVED
Closed: 7 days ago
Resolution: --- → WONTFIX

Reopening - the youtube playback benchmark is intended to test playback performance. It was never intended to be a live site test, see comment 0 - it's only currently a live site test due to caching limitations.

Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Severity: S3 → S4
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.