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

Issue 855510 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 855473
Owner:
Last visit > 30 days ago
Closed: Jun 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.3% regression in thread_times.tough_compositor_cases at 567054:567219

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

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

android-one
Project Member

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

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

Surface synchronization: Plumb more things through RenderFrameMetadata by fsamuel@chromium.org
https://chromium.googlesource.com/chromium/src/+/4576fad344baac5eb8821459489a9c0f792576e9
66.11 → 68.11 (+1.996)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 855473
Status: Duplicate (was: Assigned)

Sign in to add a comment