New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 904306 link

Starred by 1 user
Status: Assigned
Owner:
█ hpayer@chromium.org
Last visit > 30 days ago
Cc:
█ kozyatinskiy@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

34.8%-71.1% regression in v8.browsing_mobile at 604601:604656

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

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

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

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


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

Android Nexus5 Perf

v8.browsing_mobile - Benchmark documentation link:
  None
Project Member

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

Cc: kozyatinskiy@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14ddcbcfe40000

inspector: move injected script source to native by kozyatinskiy@chromium.org
https://chromium.googlesource.com/v8/v8/+/7e079c660b686d916ed5cd88bfa4ecf597300193
v8-gc-latency-mark-compactor: 25.46 → 37.19 (+11.72)

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

Benchmark documentation link:
  None
►

Sign in to add a comment