New issue
Advanced search Search tips

Issue 881802 link

Starred by 1 user
Status: WontFix
Owner:
mvstan...@chromium.org
Closed: Oct 18
Cc:
mvstan...@chromium.org
ftang@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

9.3%-11.6% regression in memory.desktop at 588771:588852

Project Member Reported by mvstan...@chromium.org, Sep 7 
See the link to graphs below.
Project Member

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

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

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


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

Win 7 Perf

memory.desktop - Benchmark documentation link:
  None
Project Member

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

Cc: ftang@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/142921b5640000

[Intl] Move NumberFormat to JSNumberFormat by ftang@chromium.org
https://chromium.googlesource.com/v8/v8/+/9c7ec98a906e5bfe259c4d913c9115f0b52e90d2
6.922e+06 → 7.971e+06 (+1.049e+06)

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

Benchmark documentation link:
  None

Comment 4 by mvstan...@chromium.org, Oct 18

Status: WontFix (was: Assigned)
Recovered graph.
►

Sign in to add a comment