New issue
Advanced search Search tips

Issue 760524 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 759392
Owner:
Closed: Aug 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regressions caused by revert of concurrent marking

Project Member Reported by ulan@google.com, Aug 30 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 30 2017

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

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


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

chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 30 2017

Mergedinto: 759392
Status: Duplicate (was: Assigned)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Michael Hablich
  Commit : f165dfdd5cb7d177de36b9fb87922ef19bb6e001
  Date   : Thu Aug 24 07:52:10 2017
  Subject: Revert "[heap] Enable concurrent marking for x86 and x64."

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_sum/browse_media/browse_media_flickr_infinite_scroll
  Change       : 269.04% | 39.9798333333 -> 147.542333333

Revision                           Result                  N
chromium@496995                    39.9798 +- 2.44284      6      good
chromium@497007                    41.1792 +- 9.03023      6      good
chromium@497013                    39.9387 +- 17.3906      6      good
chromium@497014                    43.259 +- 11.6862       6      good
chromium@497014,v8@f165dfdd5c      147.401 +- 3.3538       6      bad       <--
chromium@497014,v8@94e1437f76      143.367 +- 9.24344      6      bad
chromium@497014,v8@237f0f3271      144.981 +- 5.89716      6      bad
chromium@497015                    142.511 +- 38.0586      6      bad
chromium@497016                    146.28 +- 6.67149       6      bad
chromium@497018                    156.308 +- 68.4496      6      bad
chromium@497040                    147.542 +- 5.50478      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.flickr.infinite.scroll v8.runtimestats.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8969838751356855664


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment