New issue
Advanced search Search tips

Issue 857077 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

30.7% regression in system_health.common_mobile at 566934:567055

Project Member Reported by nzolghadr@chromium.org, Jun 27 2018

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

android-nexus5X
Project Member

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

Cc: sadrul@chromium.org
Owner: sadrul@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11d701cb240000

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

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

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

Status: WontFix (was: Assigned)
As the CL description says, timetofirst*paint is expected to go up.

Sign in to add a comment