New issue
Advanced search Search tips

Issue 789456 link

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



Sign in to add a comment

9.7% regression in v8.browsing_mobile at 518221:518302

Project Member Reported by jgruber@chromium.org, Nov 29 2017 
See the link to graphs below.
Project Member

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

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

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


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

android-nexus7v2
Project Member

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


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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/browse_media/browse_media_facebook_photos

Revision             Result                   N
chromium@518220      9905765 +- 1201615       21      good
chromium@518302      10350617 +- 2987200      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.facebook.photos v8.browsing_mobile

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

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


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

Comment 6 by 42576172...@developer.gserviceaccount.com, Nov 30 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: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/browse_media/browse_media_facebook_photos
  Change       : 8.94% | 9915312.57143 -> 10804129.1429

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/61bb5cc5255b50e27da51cd2e0a84e1a0d3dacb0..f14470c6eac37b2c1602c4e231bd894f0b05eddc


Revision             Result                   N
chromium@518220      9915313 +- 1055951       14       good
chromium@518260      9856289 +- 599873        14       good
chromium@518280      9881832 +- 1174260       21       good
chromium@518282      9796143 +- 144872        6        good
chromium@518283      ---                      ---      build failure
chromium@518284      10666415 +- 1391561      6        bad
chromium@518285      10602533 +- 2372003      14       bad
chromium@518290      10552759 +- 1676180      9        bad
chromium@518300      10599968 +- 2940647      21       bad
chromium@518381      10602686 +- 2513657      14       bad
chromium@518544      10804129 +- 506501       14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.facebook.photos v8.browsing_mobile

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

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


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

Comment 8 by 42576172...@developer.gserviceaccount.com, Dec 1 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 125509a7840623b775e3a718fefac2412d584380
  bad_revision : 9b40d51095760e7c05fbf321f6f231a72b3ef012

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/browse_media/browse_media_facebook_photos

Revision             Result                   N
chromium@518220      9946290 +- 964908        14       good
chromium@518302      10180821 +- 2801131      21       good
chromium@518346      10086625 +- 2283881      14       good
chromium@518366      10223865 +- 2291942      14       good
chromium@518370      10164652 +- 1999560      14       good
chromium@518371      ---                      ---      build failure
---                  ---                      ---      too many build failures to list
chromium@518381      ---                      ---      build failure
chromium@518382      10845397 +- 1973574      14       bad
chromium@518544      10832625 +- 155275       6        bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.facebook.photos v8.browsing_mobile

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

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


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

Comment 10 by 42576172...@developer.gserviceaccount.com, Dec 1 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: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/browse_media/browse_media_facebook_photos
  Change       : 9.19% | 9919897.42857 -> 10898748.6667

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/797dde20040933204cf4288f8630807d449b884a..4ca16519443184833fe0653ed552de88156dc6fa


Revision             Result                   N
chromium@518220      9919897 +- 951452        14       good
chromium@518261      9797342 +- 145124        6        good
chromium@518281      9808451 +- 675004        14       good
chromium@518282      ---                      ---      build failure
chromium@518283      10474642 +- 3121166      21       bad
chromium@518284      10421385 +- 2981755      21       bad
chromium@518286      10584809 +- 2465062      14       bad
chromium@518291      10510898 +- 3056104      21       bad
chromium@518302      10991714 +- 1598229      14       bad
chromium@518382      10876473 +- 1726364      14       bad
chromium@518544      10898749 +- 515388       6        bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.facebook.photos v8.browsing_mobile

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

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


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

Comment 11 by 42576172...@developer.gserviceaccount.com, Dec 2 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: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/browse_media/browse_media_facebook_photos
  Change       : 8.06% | 9965347.71429 -> 10766092.8571

Suspected Commit Range
  5 commits in range
  https://chromium.googlesource.com/chromium/src/+log/84c9ecb20735c69ed258ac33b8208b8c99365866..8381b6e1f7fb5c0cf1245f6bdd0b4d78f00e1a6b


Revision             Result                   N
chromium@518220      9965348 +- 1224241       14       good
chromium@518260      9977054 +- 921498        9        good
chromium@518280      9851164 +- 645045        14       good
chromium@518285      10256489 +- 2607620      14       good
chromium@518286      ---                      ---      build failure
chromium@518287      ---                      ---      build failure
chromium@518288      ---                      ---      build failure
chromium@518289      ---                      ---      build failure
chromium@518290      10691192 +- 2310973      14       bad
chromium@518300      10789831 +- 1858639      9        bad
chromium@518383      10692926 +- 2252839      14       bad
chromium@518544      10766093 +- 341341       14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.facebook.photos v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Comment 13 by jgruber@chromium.org, Dec 4 2017

Status: WontFix (was: Untriaged)
Kicking off another bisect but closing as return to baseline just in case it fails again.
Project Member

Comment 14 by 42576172...@developer.gserviceaccount.com, Dec 4 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: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/browse_media/browse_media_facebook_photos
  Change       : 9.64% | 9851115.42857 -> 10835706.8571

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/chromium/src/+log/092530bf6b58e5b80e3901db05bf72aca56851e1..8381b6e1f7fb5c0cf1245f6bdd0b4d78f00e1a6b


Revision             Result                   N
chromium@518220      9851115 +- 598418        14       good
chromium@518261      9812461 +- 265612        9        good
chromium@518281      9856788 +- 387788        14       good
chromium@518286      10271879 +- 2425886      14       good
chromium@518287      ---                      ---      build failure
chromium@518288      ---                      ---      build failure
chromium@518289      ---                      ---      build failure
chromium@518290      10712830 +- 2439272      14       bad
chromium@518301      10648487 +- 2149659      14       bad
chromium@518383      10692732 +- 1757918      9        bad
chromium@518544      10835707 +- 299167       14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.facebook.photos v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment