New issue
Advanced search Search tips

Issue 913513 link

Starred by 2 users
Status: WontFix
Owner:
mlippautz@chromium.org
Closed: Jan 7
Cc:
npm@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

18.3% regression in system_health.memory_desktop at 613040:613070

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 10 

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

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


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

mac-10_12_laptop_low_end-perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 11

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

[heap] Fix context disposal heap limit by mlippautz@chromium.org
https://chromium.googlesource.com/v8/v8/+/5748a22fa06599f848c27fbc118f8f6ac0882011
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 1.038e+07 → 1.175e+07 (+1.369e+06)

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

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

Comment 4 by mlippautz@chromium.org, Jan 7

Cc: -mlippautz@chromium.org
Status: WontFix (was: Assigned)
Tradeoff.
►

Sign in to add a comment