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

Issue 895296 link

Starred by 1 user
Status: WontFix
Owner:
█ hpayer@chromium.org
Last visit > 30 days ago
Closed: Oct 23
Cc:
█ hpayer@chromium.org
npm@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.4% regression in system_health.memory_desktop at 599508:599514

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

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

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

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


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

Win 7 Nvidia GPU Perf

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

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

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

[heap] Externalize mark bitmap. by hpayer@chromium.org
https://chromium.googlesource.com/v8/v8/+/17890f67fbd1cafa33f472559f09a1fad70993ce
memory:chrome:all_processes:reported_by_chrome:malloc:effective_size: 4.257e+07 → 4.402e+07 (+1.454e+06)

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

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

Comment 4 by hpayer@chromium.org, Oct 23

Status: WontFix (was: Assigned)
This CL shifts memory around: from V8 heap to malloc. Should be the same in overall.
►

Sign in to add a comment