New issue
Advanced search Search tips

Issue 900142 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Oct 30
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.2% regression in system_health.memory_desktop at 603038:603112

Project Member Reported by jgruber@chromium.org, Oct 30

Issue description

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

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


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

Win 7 Perf

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

Streams: Get MessageChannel-related values from bindings by ricea@chromium.org
https://chromium.googlesource.com/chromium/src/+/821303d2ee44304dc272587ce1513ae0a9e30d0d
memory:chrome:all_processes:reported_by_chrome:v8:effective_size: 1.072e+07 → 1.135e+07 (+6.291e+05)

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

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

Sign in to add a comment