New issue
Advanced search Search tips

Issue 871947 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 871406
Owner:
Closed: Aug 11
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.2% regression in memory.desktop at 579632:579714

Project Member Reported by chiniforooshan@chromium.org, Aug 7

Issue description

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

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


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

mac-10_13_laptop_high_end-perf
Cc: ccameron@chromium.org
Owner: ccameron@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/125c3c00640000

MacViews: Push VSync parameters from RHWVMac to BridgedNativeView by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/9eed7b76473c66cbdc5a9436c1a1a6aec851cc95
3.413e+07 → 3.512e+07 (+9.839e+05)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 871406
Status: Duplicate (was: Assigned)
Respecting VSync will change performance, also,  issue 871406  was already filed on this CL (again)

Sign in to add a comment