New issue
Advanced search Search tips

Issue 898898 link

Starred by 1 user
Status: Duplicate
Merged: issue 899002
Owner:
backer@chromium.org
Closed: Oct 25
Cc:
backer@chromium.org
maxlg@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-57% regression in system_health.memory_desktop at 600258:600526

Project Member Reported by maxlg@chromium.org, Oct 25 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 25 

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

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


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

Win 7 Nvidia GPU Perf
Win 7 Perf
mac-10_13_laptop_high_end-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 25

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

Bound time to delete cc::Resource by backer@chromium.org
https://chromium.googlesource.com/chromium/src/+/9bf42619ce76159d90ab4b968208ad620c042ac2
memory:chrome:all_processes:reported_by_chrome:cc:effective_size: 7.221e+07 → 1.265e+08 (+5.426e+07)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

Comment 4 by backer@chromium.org, Oct 25

Mergedinto: 899002
Status: Duplicate (was: Assigned)
►

Sign in to add a comment