Confirmed users
156
edits
Buildbot/Talos/Tests: Difference between revisions
rasterflood tests
Daosheng Mu (talk | contribs) |
(rasterflood tests) |
||
| Line 1,601: | Line 1,601: | ||
This measures the amount of time it takes to render a page after changing its display list. The page has a large number of display list items (10,000), and mutates one every frame. The goal of the test is to make displaylist construction a bottleneck, rather than painting or other factors, and thus improvements or regressions to displaylist construction will be visible. The test runs in ASAP mode to maximize framerate, and the result is how quickly the test was able to mutate and re-paint 600 items, one during each frame. | This measures the amount of time it takes to render a page after changing its display list. The page has a large number of display list items (10,000), and mutates one every frame. The goal of the test is to make displaylist construction a bottleneck, rather than painting or other factors, and thus improvements or regressions to displaylist construction will be visible. The test runs in ASAP mode to maximize framerate, and the result is how quickly the test was able to mutate and re-paint 600 items, one during each frame. | ||
==== Possible regression causes ==== | |||
* None listed yet. If you fix a regression for this test and have some tips to share, this is a good place for them. | |||
=== rasterflood_svg === | |||
* contact: :dvander | |||
* source: [[https://searchfox.org/mozilla-central/source/testing/talos/talos/tests/gfx/benchmarks/rasterflood_svg.html rasterflood_svg.html]] | |||
* type: [https://wiki.mozilla.org/Buildbot/Talos#Page_Load_Tests PageLoader] | |||
* data: we load the rasterflood_svg.html page ten times, measuring pageload each time, generating 10 data points. | |||
* summarization: | |||
** subtest: [https://wiki.mozilla.org/Buildbot/Talos/Data#ignore_first ignore first] data point, then take the [https://wiki.mozilla.org/Buildbot/Talos/Data#median median] of the remaining 9; [https://dxr.mozilla.org/mozilla-central/source/testing/talos/talos/test.py#l986 source: test.py] | |||
This page animates some complex SVG patterns in a requestAnimationFrame callback. However, it also churns the CPU during each callback, spinning an empty loop for 14ms each frame. The intent is that, if we consider the rasterization costs to be 0, then the animation should run close to 60fps. Otherwise it will lag. Since rasterization costs are not 0, the lower we can get them, the faster the test will run. The test runs in ASAP mode to maximize framerate. The result is how quickly the browser is able to render 600 frames of the animation. | |||
Improvements (or regressions) to general painting performance or SVG are likely to affect this benchmark. | |||
==== Possible regression causes ==== | |||
* None listed yet. If you fix a regression for this test and have some tips to share, this is a good place for them. | |||
=== rasterflood_gradient === | |||
* contact: :dvander | |||
* source: [[https://searchfox.org/mozilla-central/source/testing/talos/talos/tests/gfx/benchmarks/rasterflood_gradient.html rasterflood_gradient.html]] | |||
* type: [https://wiki.mozilla.org/Buildbot/Talos#Page_Load_Tests PageLoader] | |||
* data: we load the rasterflood_gradient.html page ten times, computing a score each time, generating 10 data points. | |||
* summarization: | |||
** subtest: [https://wiki.mozilla.org/Buildbot/Talos/Data#ignore_first ignore first] data point, then take the [https://wiki.mozilla.org/Buildbot/Talos/Data#median median] of the remaining 9; [https://dxr.mozilla.org/mozilla-central/source/testing/talos/talos/test.py#l986 source: test.py] | |||
This page animates some complex gradient patterns in a requestAnimationFrame callback. However, it also churns the CPU during each callback, spinning an empty loop for 14ms each frame. The intent is that, if we consider the rasterization costs to be 0, then the animation should run close to 60fps. Otherwise it will lag. Since rasterization costs are not 0, the lower we can get them, the faster the test will run. The test runs in ASAP mode to maximize framerate. | |||
The test runs for 10 seconds, and the resulting score is how many frames we were able to render during that time. Higher is better. Improvements (or regressions) to general painting performance or gradient rendering will affect this benchmark. | |||
==== Possible regression causes ==== | ==== Possible regression causes ==== | ||
* None listed yet. If you fix a regression for this test and have some tips to share, this is a good place for them. | * None listed yet. If you fix a regression for this test and have some tips to share, this is a good place for them. | ||