TestEngineering/Performance: Difference between revisions

Jump to navigation Jump to search

TestEngineering/Performance (view source)

Revision as of 13:41, 5 August 2019

2,113 bytes removed ,  5 August 2019
→‎Objectives
No edit summary
Line 49: Line 49:
* KR4.2: Power tests on macOS laptops [sparky] {{ok|}} [100%]
* KR4.2: Power tests on macOS laptops [sparky] {{ok|}} [100%]
* KR6.6: Improve perf sheriff efficiency [igoldan] {{ok|}} [70%]
* KR6.6: Improve perf sheriff efficiency [igoldan] {{ok|}} [70%]
=== 2019/H1 ===
* Increase regression detection '''coverage''' to page load on Android products including WebView comparisons
* Increase quality standards by measuring and alerting on power usage for Android and ARM64
* Build dashboards to improve '''visibility''' of how we are tracking against our release criteria for Android
* Reducing noise in test results and adding annotations to provide '''clarity''' of signal for regressions
* Develop measurements and mechanisms for reporting on our tools, policies and documentation for how to improve '''clarity''' and '''efficiency''' of risk assessments
=== [https://docs.google.com/spreadsheets/d/1P1d7rzA27t3OHljraxapNgDl-1Hsc_novoj78w8qog0/edit#gid=104649774 2019/Q2] ===
* Meet Fenix blocking performance release criteria
** Fenix 1.0 geo mean cold page load time to onload event is >20% faster than Fennec 64 for tp6m reference sites (2019Q1 snapshots) on Fenix reference hardware
* Perform well on priority use cases for Qualcomm's H2 product launches
** Firefox v68 for Windows 10 on ARM battery utilization is within 20% of Edge on Qualcomm 8xx series reference hardware when watching the tp6m YouTube reference video to completion
** The proportion of dropped frames during playback of the tp6m YouTube reference video at 1080p resolution does not exceed 4% on Firefox v68 on the Qualcomm 8xx series reference hardware.
** Firefox v68 for Windows 10 on ARM geomean cold page load time to the onload event is within 20% of Edge for tp6 reference sites on Qualcomm 8xx series reference hardware.
* Meet blocking performance objectives for GeckoView-powered Fire TV pitch
** The proportion of dropped frames during playback of the tp6m 4K YouTube reference video using GeckoView-powered Firefox for Fire TV does not exceed 4% on the Fire TV 4k stick.
* Lay foundation to support performance work in H2
** Develop key metrics and scenarios needed to build CI-integrated tests for at least three of video quality, scroll responsiveness, input responsiveness, memory use, CPU utilization, and heat.
* Make the Firefox desktop browser feel fast and responsive


== Projects ==
== Projects ==
Davehunt
Confirmed users
2,197

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1215937"

Navigation menu