New issue
Advanced search Search tips

Issue 769716 link

Starred by 1 user
Status: WontFix
Owner:
u...@chromium.org
Closed: Nov 2017
Cc:
hablich@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 4% regression in v8.runtimestats.browsing_desktop at 502499:503862

Project Member Reported by hablich@chromium.org, Sep 28 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 28 2017 

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

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


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

chromium-rel-mac11-pro
chromium-rel-win7-dual
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

Comment 3 Deleted

Comment 4 by dtu@chromium.org, Sep 28 2017 

#3: Filed https://github.com/catapult-project/catapult/issues/3931 for the error.
I'll re-run the job.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Sep 29 2017 

📍 Pinpoint job completed.
https://pinpoint-dot-chromeperf.appspot.com/job/16eae01c780000

Found significant differences after 1 commit:

Reland "[heap] Enable concurrent marking for x86 and x64."
By ulan@chromium.org · Thu Sep 21 12:35:10 2017
v8@a76d0a771e430dbc8716624febc549aede738d96

Comment 7 by hablich@chromium.org, Sep 29 2017

Owner: u...@chromium.org
Status: Assigned (was: Untriaged)

Comment 8 by u...@chromium.org, Nov 21 2017

Status: WontFix (was: Assigned)
I guess concurrent marker and concurrent compilation are competing for the background threads here. Not actionable.
►

Sign in to add a comment