New issue
Advanced search Search tips

Issue 879759 link

Starred by 1 user
Status: WontFix
Owner:
mstarzinger@chromium.org
Closed: Sep 3
Cc:
ericrk@chromium.org
mstarzinger@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.5% regression in system_health.common_desktop at 587190:587262

Project Member Reported by ericrk@chromium.org, Aug 31 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 31 

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

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


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

mac-10_13_laptop_high_end-perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 1

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

[wasm] Brush up unittests for kExprThrow. by mstarzinger@chromium.org
https://chromium.googlesource.com/v8/v8/+/edeac2917159998e8bb38e0f53f6d01f3931dfba
533.8 → 514.1 (-19.72)

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

Comment 4 by mstarzinger@chromium.org, Sep 3

Status: WontFix (was: Assigned)
The change in question touches V8 unit-tests only. The code is never compiled into Chrome. I doubt that the change could affect any metrics in Chrome.
►

Sign in to add a comment