New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 901951 link

Starred by 1 user
Status: Closed
Owner:
wfh@chromium.org
Closed: Nov 12
Cc:
█ gmx@chromium.org
wfh@chromium.org
tdres...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.9%-10.4% regression in system_health.memory_desktop at 605071:605107

Project Member Reported by tdres...@chromium.org, Nov 5 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 5 

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

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


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

linux-perf

memory.desktop - Benchmark documentation link:
  None

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 5

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

Use new tcmalloc on Linux builds by default. by wfh@chromium.org
https://chromium.googlesource.com/chromium/src/+/f7c11345ee40e3c8a4f281cbf82295ca5231d118
memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size: 1.31e+08 → 1.436e+08 (+1.264e+07)

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

Benchmark documentation link:
  None

Comment 4 by wfh@chromium.org, Nov 12

Cc: gmx@chromium.org
Status: Closed (was: Assigned)
this was already reverted so closing this. it can be re-opened again if necessary when it gets relanded.
►

Sign in to add a comment