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

Issue 874434 link

Starred by 1 user
Status: Duplicate
Merged: issue 874437
Owner:
█ hpayer@chromium.org
Last visit > 30 days ago
Closed: Aug 16
Cc:
cbruni@google.com
█ hpayer@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

27.9%-163% regression in v8.browsing_mobile at 582986:583026

Project Member Reported by cbruni@google.com, Aug 15 
See the link to graphs below.
Project Member

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

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

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


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

Android Nexus6 WebView Perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 16

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

[heap] Use std::atomic for page flags. by hpayer@chromium.org
https://chromium.googlesource.com/v8/v8/+/7f3f7e8a9547ece1a7f80ce902bc23632e902b0b
3.513 → 7.741 (+4.228)

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

Comment 4 by hpayer@chromium.org, Aug 16

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

Sign in to add a comment