New issue
Advanced search Search tips

Issue 901756 link

Starred by 1 user
Status: Duplicate
Owner:
oysteine@chromium.org
Closed: Nov 7
Cc:
jgruber@chromium.org
oysteine@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

17.8%-494% regression in v8.browsing_mobile at 603867:604385

Project Member Reported by jgruber@chromium.org, Nov 5 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 5 

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

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


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

Android Nexus6 WebView Perf
android-nexus5x-perf

v8.browsing_mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 5

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

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea
v8-gc-full-mark-compactor: 18.24 → 28.62 (+10.38)

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

Benchmark documentation link:
  None

Comment 4 by oysteine@chromium.org, Nov 7

Mergedinto: 901754
Status: Duplicate (was: Assigned)
►

Sign in to add a comment