New issue
Advanced search Search tips

Issue 913456 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner:
Closed: Dec 12
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.5%-9.4% regression in system_health.memory_desktop at 613910:614208

Project Member Reported by petermarshall@google.com, Dec 10

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=913456

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


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

Win 7 Nvidia GPU Perf
linux-perf
mac-10_13_laptop_high_end-perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: u...@chromium.org
Owner: u...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/151176f4140000

Do not pretenure descriptor arrays. by ulan@chromium.org
https://chromium.googlesource.com/v8/v8/+/92e228534a472c5ff55f7ed536f5c6ba7daccedb
memory:chrome:all_processes:reported_by_chrome:v8:effective_size: 2.254e+07 → 2.447e+07 (+1.926e+06)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Mergedinto: 913482
Status: Duplicate (was: Assigned)

Sign in to add a comment