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

Issue 874897 link

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



Sign in to add a comment

11.4% regression in octane at 582986:583026

Project Member Reported by tdres...@chromium.org, Aug 16 
See the link to graphs below.
Project Member

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

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

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


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

Android Nexus6 WebView Perf
Project Member

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

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/14869c0c640000

[heap] Use std::atomic for page flags. by hpayer@chromium.org
https://chromium.googlesource.com/v8/v8/+/7f3f7e8a9547ece1a7f80ce902bc23632e902b0b
3081 → 2762 (-319.5)

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

Comment 4 by hpayer@chromium.org, Aug 21

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

Sign in to add a comment