New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 697892 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Android startup benchmarks slowly trending upwards, on ref build as well as ToT

Project Member Reported by sullivan@chromium.org, Mar 2 2017

Issue description

Ben and I noticed an upward trend on start_with_url.cold.startup_pages on perf-clankium-l-phone, and checked the graph for the N5 on the public waterfall because it has ref builds. We do see the same upward trend, both in ToT and in ref builds:

https://chromeperf.appspot.com/report?sid=2e0366ec5332699105e44239fc5afc089427c086aebb0f6236ac06db17db84a0&num_points=800

I see this in the majority of devices. I'm not sure that we have enough people working on android startup to get to the bottom of it, unfortunately. pasko, any quick thoughts on things to check for in our test setup?
 

Comment 1 by pasko@chromium.org, Mar 6 2017

Both upward trends are not surprising.

For ref: eMMC on the device gets fragmented and weared, which makes it slower. We may double-check that the framework is doing TRIM (which it may not due to devices being busy around the clock).

For trunk: worse upward trend than ref, this could be because of the binary size growth .. or .. something else. We could take another look with more precise tooling to make a few one-off improvements as we did before, but the upwards trend will probably continue.
Labels: Performance-Loading
Labels: -Performance-Loading Performance-Browser
Status: Fixed (was: Untriaged)
Not sure what happened, but this isn't slowly increasing over time anymore.

Sign in to add a comment