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

Issue 808649 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1%-41.3% regression in loading.desktop at 532680:532829

Project Member Reported by npm@chromium.org, Feb 2 2018

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=808649

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


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

chromium-rel-win10
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
win-high-dpi
Cc: fsam...@chromium.org sky@chromium.org samans@chromium.org
Owner: fsam...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/168a8d4e840000

Surface synchronization: Reduce synchronization deadline for navigation by fsamuel@chromium.org
chromium @ b46e0efc8062d290e0657c12f22d0453dfd94188

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
It seems like this regressed the first time when we started allocating new surfaces on navigation.
 Issue 808644  has been merged into this issue.
 Issue 808619  has been merged into this issue.
Labels: -M-66 M-67
Mergedinto: 808650
Status: Duplicate (was: Assigned)

Sign in to add a comment