New issue
Advanced search Search tips

Issue 897704 link

Starred by 1 user
Status: Duplicate
Merged: issue 897703
Owner: ----
Closed: Oct 22
Cc:
backer@chromium.org
hjd@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

21.1% regression in system_health.memory_desktop at 600326:600401

Project Member Reported by hjd@google.com, Oct 22 
See the link to graphs below.
Project Member

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

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

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


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

Win 7 Perf

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

Comment 3 by hjd@google.com, Oct 22

Mergedinto: 897703
Status: Duplicate (was: Untriaged)
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Oct 22

Cc: backer@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15d07c82e40000

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: 1.129e+07 → 1.304e+07 (+1.751e+06)

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

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

Sign in to add a comment