New issue
Advanced search Search tips

Issue 906051 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.7%-75.7% regression in v8.browsing_desktop at 608126:608167

Project Member Reported by petermarshall@google.com, Nov 16

Issue description

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

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


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

linux-perf

v8.browsing_desktop - Benchmark documentation link:
  None
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/112721b0140000
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/1615f34be40000
Status: WontFix (was: Untriaged)
Cc: fergal@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/111409d3e40000

Add a testing configuration for HTMLParsingYieldTime study. by fergal@chromium.org
https://chromium.googlesource.com/chromium/src/+/e2fadf24cd0c2c40009b1eb60e38f5ff3e3c859e
memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size: 1.038e+08 → 1.214e+08 (+1.763e+07)

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

Benchmark documentation link:
  None

Sign in to add a comment