Performance/Fenix/Performance reviews: Difference between revisions

Jump to navigation Jump to search
→‎Testing Start Up code: clean up start up paths
(→‎Testing Start Up code: Correct analyze durations)
(→‎Testing Start Up code: clean up start up paths)
Line 7: Line 7:
# From [https://github.com/mozilla-mobile/perf-tools the <code>mozilla-mobile/perf-tools</code> repository], use <code>measure_start_up.py</code>.<br>The arguments for start-up should include your target (<code>Fenix</code> or <code>Focus</code>).  
# From [https://github.com/mozilla-mobile/perf-tools the <code>mozilla-mobile/perf-tools</code> repository], use <code>measure_start_up.py</code>.<br>The arguments for start-up should include your target (<code>Fenix</code> or <code>Focus</code>).  
# Determine the start-up path that your code affects this could be:
# Determine the start-up path that your code affects this could be:
## <code>cold_main_first_frame</code>: This is the first frame drawn by the application. This path is taken by all "type" of start-ups
## <code>cold_main_first_frame</code>: when clicking the app's homescreen icon, this is the duration from process start until the first frame drawn
## <code>cold_view_nav_start</code>: This path is taken when the browser is opened through an outside link (i.e: a link opened through Ggmail)
## <code>cold_view_nav_start</code>: when opening the browser through an outside link (e.g. a link in gmail), this is the duration from process start until roughly Gecko's Navigation::Start event
#After determining the path your changes affect, these are the steps that you should follow:
# After determining the path your changes affect, these are the steps that you should follow:


Example:
Example:
Confirmed users
975

edits

Navigation menu