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

Issue 854513 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.7%-79.2% regression in system_health.common_mobile at 566884:567055

Project Member Reported by alexclarke@chromium.org, Jun 20 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 20 2018

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=854513

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=9b06651c859fb44a4b1123d86a76f707c2fd845140515dbe635e6ee70ba2906b


Bot(s) for this bug's original alert(s):

android-nexus5
android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 20 2018

Cc: sadrul@chromium.org
Owner: sadrul@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/12d53afd240000

Reland "paint timing: Use presentation-time instead of swap-time." by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/992979a662b28e7b9a62419f87b1839557611efc
272.1 → 456.9 (+184.8)

presentation feedback: Use a GLFence fallback. by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/3821fdf5c54add24d02adef248a311c293ea0bd0
548.4 → 479.9 (-68.47)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 4 by sadrul@chromium.org, Jun 20 2018

Status: WontFix (was: Assigned)
timetofirstpaint is expected to grow with that change (not a regression, it changes how the metric is measured).

Sign in to add a comment