New issue
Advanced search Search tips

Issue 776298 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 775864
Owner: ----
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

52.2% regression in v8.runtimestats.browsing_desktop at 509188:509256

Project Member Reported by jgruber@chromium.org, Oct 19 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 19 2017

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

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


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

chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 19 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_search/browse_search_google_india

Revision             Result                  N
chromium@509187      2.23471 +- 1.59919      21      good
chromium@509256      2.21224 +- 2.11094      21      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.search.google.india 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/8965319649188415968


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Oct 19 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_search/browse_search_google_india

Revision             Result                  N
chromium@509097      2.14186 +- 1.82619      21      good
chromium@509256      2.32481 +- 2.35591      21      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.search.google.india 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/8965309323429306064


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Oct 20 2017

Mergedinto: 775864
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Michael Lippautz
  Commit : 4b42656dd6fca982c60185c004e2648093d70b51
  Date   : Mon Oct 16 10:00:08 2017
  Subject: [heap] Unify incremental and main marking visitor

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_media/browse_media_youtube
  Change       : 89.73% | 6.64633333333 -> 12.6098333333

Revision                           Result                  N
chromium@509125                    6.64633 +- 3.08615      6      good
chromium@509166                    6.774 +- 1.56757        6      good
chromium@509176                    6.47867 +- 2.44191      6      good
chromium@509181                    7.08933 +- 2.25403      6      good
chromium@509184                    7.39267 +- 3.08647      6      good
chromium@509185                    6.218 +- 1.8269         6      good
chromium@509185,v8@4b42656dd6      12.8647 +- 3.35919      6      bad       <--
chromium@509185,v8@089dd7d244      13.0643 +- 1.43621      6      bad
chromium@509185,v8@5820041884      12.7905 +- 1.91831      6      bad
chromium@509185,v8@e659f45610      13.2602 +- 1.92496      6      bad
chromium@509185,v8@af49af006f      13.6385 +- 2.78569      6      bad
chromium@509186                    12.9545 +- 3.26308      6      bad
chromium@509206                    12.6098 +- 1.67102      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.youtube 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/8965232392319105216


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Oct 20 2017


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-scavenger_avg/browse_tech/browse_tech_discourse_infinite_scroll
  Change       : 13.14% | 1.22836517398 -> 1.38975570957

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/90f3798437977568d0577fa422d94471fed387e4..5f889022f1e61bace2efa5d54f6da3cae0402ad2


Revision             Result                    N
chromium@509170      1.22837 +- 0.591172       14       good
chromium@509179      1.19158 +- 0.116876       21       good
chromium@509184      1.18589 +- 0.110535       14       good
chromium@509185      1.16801 +- 0.0769559      6        good
chromium@509186      ---                       ---      build failure
chromium@509187      ---                       ---      build failure
chromium@509188      1.47242 +- 1.11611        14       bad
chromium@509204      1.27573 +- 0.698812       14       bad
chromium@509237      1.38976 +- 0.984119       14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.tech.discourse.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/8965231081655100080


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment