Confirmed users
2,197
edits
(Instructions in how to customize the gecko profiler) |
m (Davehunt moved page TestEngineering/Performance/Sheriffing/Raptor/Youtube playback performance to TestEngineering/Performance/Raptor/Youtube playback performance) |
||
(5 intermediate revisions by 3 users not shown) | |||
Line 8: | Line 8: | ||
[https://wiki.mozilla.org/Performance_sheriffing/Raptor#Running_Locally_2 general Raptor documentation] first. | [https://wiki.mozilla.org/Performance_sheriffing/Raptor#Running_Locally_2 general Raptor documentation] first. | ||
The benchmark test can be run on Firefox desktop via the following command: | |||
$ ./mach raptor-test --test=raptor-youtube-playback | $ ./mach raptor-test --test=raptor-youtube-playback | ||
To run the benchmark on the android geckoview example app, use this command: | |||
$ ./mach raptor-test --test raptor-youtube-playback-geckoview --app=geckoview --binary="org.mozilla.geckoview_example" | |||
=== Customizing the test execution === | === Customizing the test execution === | ||
Line 16: | Line 20: | ||
==== Subset of tests ==== | ==== Subset of tests ==== | ||
To only run a subset of tests the benchmark test page supports the '''tests''' argument, which allows to add any number of tests based on their index. | To only run a subset of tests the benchmark test page supports the '''tests''' argument, which allows to add any number of tests based on their index. There are two possible methods to specify the list of tests: | ||
* Run arbitrary videos, eg. of index 6, 47, and 90: | |||
test_url = http://...main.html?test_type=playbackperf-test&raptor=true&command=run&exclude=1,2&tests=6,47,90 | test_url = http://...main.html?test_type=playbackperf-test&raptor=true&command=run&exclude=1,2&tests=6,47,90 | ||
* Run a range of videos eg. from index 23 to 42 | |||
test_url = http://...main.html?test_type=playbackperf-test&raptor=true&command=run&exclude=1,2&tests=23-42 | |||
This is helpful if specific video codecs, resolutions, or playback speeds are causing performance issues. | This is helpful if specific video codecs, resolutions, or playback speeds are causing performance issues. | ||
==== Running with audio muted ==== | |||
Especially on Android the tests are running with audio muted to workaround the auto-play blocking issue as covered on [https://bugzilla.mozilla.org/show_bug.cgi?id=1547717 Bug 1547717]. | |||
If the same should be done for the desktop applications, the '''muted''' argument of the test page: | |||
test_url = http://...main.html?test_type=playbackperf-test&raptor=true&command=run&exclude=1,2&muted=true | |||
== Profiling == | == Profiling == |