Confirmed users
975
edits
Performance/Fenix/Performance reviews: Difference between revisions
Performance/Fenix/Performance reviews (view source)
Revision as of 23:04, 5 November 2021
, 5 November 2021→Timestamp benchmark: Add outline
(→Timestamp benchmark: Add outline) |
|||
| Line 58: | Line 58: | ||
== Timestamp benchmark == | == Timestamp benchmark == | ||
A timestamp benchmark is a manual test where a developer adds temporary code to log the duration they want to measure and then performs the use case on the device themselves to get the values printed. Like automated benchmarks, these tests can accurately measure what users experience. They are fairly quick to write and execute but are tedious and time-consuming to carry out, especially more than once, and have many places where errors can be introduced. | A timestamp benchmark is a manual test where a developer adds temporary code to log the duration they want to measure and then performs the use case on the device themselves to get the values printed. Like automated benchmarks, these tests can accurately measure what users experience. They are fairly quick to write and execute but are tedious and time-consuming to carry out, especially more than once, and have many places where errors can be introduced. | ||
To help you perform one of these yourself, let's walk through '''an example timestamp benchmark'''. Here's an '''outline''' of our task: | |||
# Decide the duration you want to measure | |||
# Do the following once for the commit before your changes and once for the commit after your changes... | |||
## Add code to measure the duration | |||
## Install & run the use case several times | |||
## Capture the results from logcat | |||
# Compare the results, generally by comparing the ''median'' of the two runs | |||
== Profile == | == Profile == | ||
TODO | TODO | ||