New issue
Advanced search Search tips

Issue 896816 link

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

Blocking:
issue 898270



Sign in to add a comment

1.3%-16.1% regression in memory:chrome:all_processes:reported_by_chrome:malloc:effective_size at 600385:600423

Project Member Reported by 42576172...@developer.gserviceaccount.com, Oct 18 
See the link to graphs below.
Project Member

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

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

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


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 18

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/12b3c546e40000

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.206e+08 → 1.416e+08 (+2.103e+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