Confirmed users
372
edits
(→tresize: add possible regression causes for tresize) |
|||
Line 246: | Line 246: | ||
** subtest: [https://wiki.mozilla.org/Performance_sheriffing/Talos/Data#ignore_first ignore first] 5 data points, then take the [https://wiki.mozilla.org/Performance_sheriffing/Talos/Data#median median] of the remaining 20 data points; [https://dxr.mozilla.org/mozilla-central/source/testing/talos/talos/test.py#l734 source: test.py] | ** subtest: [https://wiki.mozilla.org/Performance_sheriffing/Talos/Data#ignore_first ignore first] 5 data points, then take the [https://wiki.mozilla.org/Performance_sheriffing/Talos/Data#median median] of the remaining 20 data points; [https://dxr.mozilla.org/mozilla-central/source/testing/talos/talos/test.py#l734 source: test.py] | ||
** suite: identical to subtest | ** suite: identical to subtest | ||
'''Important note:''' This test now requires an 'opt' build. If the perf-reftest is ran on a non-opt build, it will timeout (more specifically on innertext-1.html, and possibly others in the future). | |||
Style system performance test suite. The perf-reftest suite is a unique talos suite where each subtest loads two different test pages: a 'base' page (i.e. bloom_basic) and a 'reference' page (i.e. bloom_basic_ref), and then compares each of the page load times against eachother to determine the variance. | Style system performance test suite. The perf-reftest suite is a unique talos suite where each subtest loads two different test pages: a 'base' page (i.e. bloom_basic) and a 'reference' page (i.e. bloom_basic_ref), and then compares each of the page load times against eachother to determine the variance. |