Confirmed users
699
edits
Gecko:NewPerfHarness: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "We need a new perf harness to be used initially for testing fennec, but expected to be used more generally. The purpose of this page is to gather desiderata and come out with (a...") |
No edit summary |
||
| Line 1: | Line 1: | ||
We need a new perf harness to be used initially for testing fennec, but expected to be used more generally. The purpose of this page is to gather desiderata and come out with (a) tentative design(s) for infrastructure. Low-level details concerning specific metrics and implementation of infrastructure can be hashed out elsewhere. | We need a new perf harness to be used initially for testing fennec, but expected to be used more generally. The purpose of this page is to gather desiderata and come out with (a) tentative design(s) for infrastructure. Low-level details concerning specific metrics and implementation of infrastructure can be hashed out elsewhere. | ||
== Background == | |||
Our performance tests currently rely on metrics accessible by web content (Date.now, events, etc.). This approach is incompatible with testing performance perceived by users, because we explicitly lie to web content for perf reasons. Implementing this approach sanely is also made next-to-impossible by process separation, GPU rendering, async scrolling and animation, and async rerendering (fennec). | |||
There are additional issues with the implementation of our current test harnesses that are exarcerbated when they're run on mobile devices. The harnesses are mostly written to run on the same system as the one being tested, meaning that the tests and the harness can compete for system resources. | |||
Therefore, I claim that a new testing harness is in order. | |||
== Non-goals == | == Non-goals == | ||