New issue
Advanced search Search tips

Issue 901779 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Today
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

21.2%-46.4% regression in v8.browsing_mobile-future at 604870:604956

Project Member Reported by tebbi@chromium.org, Nov 5

Issue description

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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

v8.browsing_mobile-future - Benchmark documentation link:
  None
Cc: ftang@chromium.org
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/106db035e40000

[Intl] Clean up Intl::GetStringOption by ftang@chromium.org
https://chromium.googlesource.com/v8/v8/+/d44ed132d1faa646c18e6b99e11146ec7f0bd1cf
total:500ms_window:renderer_eqt:v8:execute: 1.772e+04 → 1.824e+04 (+527)

[Intl] Move cachedOrNewService to C++ w/o caching by ftang@chromium.org
https://chromium.googlesource.com/v8/v8/+/dffaff7769dd89670a897d1adc50639b8655bf39
total:500ms_window:renderer_eqt:v8:execute: 1.798e+04 → 2.075e+04 (+2769)

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

Benchmark documentation link:
  None

Comment 4 by tebbi@google.com, Yesterday (43 hours ago)

Owner: ftang@chromium.org

Comment 5 by ftang@chromium.org, Today (10 hours ago)

Status: Fixed (was: Assigned)
The regression caused by
https://chromium.googlesource.com/v8/v8/+/dffaff7769dd89670a897d1adc50639b8655bf39

 is already addressed by 
https://chromium-review.googlesource.com/c/v8/v8/+/1320892
in Nov 13.

Sign in to add a comment