Confirmed users
975
edits
Performance/Fenix/Profilers and Tools: Difference between revisions
Performance/Fenix/Profilers and Tools (view source)
Revision as of 19:50, 21 August 2020
, 21 August 2020Link to section headers
(Edited lists to be more readable.) |
(Link to section headers) |
||
| Line 1: | Line 1: | ||
Measuring performance has a few major approaches: | Measuring performance has a few major approaches: | ||
* Profilers and performance tooling: detailed info with some overhead | * [[#Profilers and performance tooling|Profilers and performance tooling:]] detailed info with some overhead | ||
* Timestamp measurement: precise values with no details | * [[#Timestamp measurement|Timestamp measurement:]] precise values with no details | ||
* Performance tests: | * [[#Performance tests|Performance tests:]] a WIP | ||
If you need more assistance with android performance testing, please reach out to us on the [https://chat.mozilla.org/#/room/#perf-android-frontend:mozilla.org #perf-android-frontend channel on Matrix]. | If you need more assistance with android performance testing, please reach out to us on the [https://chat.mozilla.org/#/room/#perf-android-frontend:mozilla.org #perf-android-frontend channel on Matrix]. | ||
| Line 47: | Line 47: | ||
* Use a production build variant: see the [https://github.com/mozilla-mobile/fenix/blob/master/README.md#guide-to-build-variants guide on build variants in the Fenix README] | * Use a production build variant: see the [https://github.com/mozilla-mobile/fenix/blob/master/README.md#guide-to-build-variants guide on build variants in the Fenix README] | ||
* If you’re measuring UI, you may need to measure when frames are drawn, not when lifecycle methods (e.g. onResume) are called | * If you’re measuring UI, you may need to measure when frames are drawn, not when lifecycle methods (e.g. onResume) are called | ||
== Performance tests == | |||
These aren't ready for broader use yet – please contact us for questions! | |||