New issue
Advanced search Search tips

Issue 785726 link

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



Sign in to add a comment

A zero-to-nonzero to 10.6% regression in v8.runtimestats.browsing_desktop at 514456:514807

Project Member Reported by bmeurer@google.com, Nov 16 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 16 2017 

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

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


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

chromium-rel-mac-retina
chromium-rel-win10
linux-release
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 16 2017

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

[heap] Re-enable concurrent marking.
By ulan@chromium.org · Tue Nov 07 13:11:10 2017
v8 @ 6bb1d47e6e82f75ead36cdab209afc5dafa8329c

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

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 20 2017 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/149ed963f80000

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

Status: WontFix (was: Assigned)
Optimize:duration_avg showed up during the initial landing of concurrent marking too. The only explanation I have is GC timing.

JS duration regression is unexpected, but pinpoint cannot repro it.
►

Sign in to add a comment