New issue
Advanced search Search tips

Issue 897131 link

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

Blocking:
issue 898270



Sign in to add a comment

8.9% regression in system_health.memory_desktop at 600385:600423

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

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

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

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


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

linux-perf

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

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

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/10373d5ce40000

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

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

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

Comment 4 by rjkroege@chromium.org, Oct 24

Blocking: 898270
Labels: vulkanize

Comment 5 by backer@chromium.org, Oct 25

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

Sign in to add a comment