New issue
Advanced search Search tips

Issue 719884 link

Starred by 1 user
Status: Duplicate
Merged: issue 719359
Owner: ----
Closed: May 2017
Cc:
mlippautz@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

22.7%-128.9% regression in v8.browsing_mobile at 469310:469683

Project Member Reported by mlippautz@google.com, May 9 2017 
See the link to graphs below.
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 9 2017 


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-incremental-step_max/browse_shopping/browse_shopping_lazada

Revision             Result                  N
chromium@469309      2.78581 +- 4.34159      21      good
chromium@469588      2.5569 +- 2.69597       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.shopping.lazada v8.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980082262516800944

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6386777184534528


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, May 9 2017 


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-incremental-step_max/browse_shopping/browse_shopping_lazada

Revision             Result                  N
chromium@469309      2.52352 +- 2.96308      21      good
chromium@469588      2.73186 +- 5.30618      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.shopping.lazada v8.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980058211863255312

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6386777184534528


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, May 11 2017 


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-incremental-step_max/browse_chrome/browse_chrome_newtab

Revision             Result                  N
chromium@469280      5.49324 +- 8.59476      21      good
chromium@469610      5.08719 +- 9.03576      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.chrome.newtab v8.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979951785864936400

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5774840780292096


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, May 11 2017 


=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-incremental-step_max/browse_chrome/browse_chrome_newtab

Revision             Result                  N
chromium@469280      5.68762 +- 6.43665      21       good
chromium@469321      5.86021 +- 4.33114      14       good
chromium@469341      5.62462 +- 6.59872      21       good
chromium@469351      5.24962 +- 7.26029      21       unknown
chromium@469363      ---                     ---      build failure
chromium@469364      4.52605 +- 6.22482      21       bad
chromium@469447      4.3035 +- 3.18457       14       bad
chromium@469610      4.27821 +- 3.17326      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.chrome.newtab v8.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979926096154547152

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5774840780292096


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, May 12 2017

Mergedinto: 719359
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : hpayer
  Commit : 8833af23e9788c725b0887446915e4820383a385
  Date   : Fri May 05 11:24:02 2017
  Subject: [heap] Memory reducer calls GC with kGCCallbackFlagCollectAllExternalMemory flag.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-total_avg/browse_social/browse_social_twitter
  Change       : 26.85% | 0.681952968346 -> 0.86505734404

Revision                           Result                     N
chromium@469325                    0.681953 +- 0.0632725      6      good
chromium@469518                    0.667373 +- 0.0797266      6      good
chromium@469614                    0.690917 +- 0.105833       6      good
chromium@469638                    0.659478 +- 0.0818551      6      good
chromium@469650                    0.670581 +- 0.0944699      6      good
chromium@469653                    0.681131 +- 0.0910801      6      good
chromium@469654                    0.678155 +- 0.0533471      6      good
chromium@469654,v8@25959abf79      0.66695 +- 0.0592842       6      good
chromium@469654,v8@b7b3781b87      0.673808 +- 0.0955412      6      good
chromium@469654,v8@8833af23e9      0.862467 +- 0.0659266      6      bad       <--
chromium@469655                    0.845035 +- 0.0578928      6      bad
chromium@469656                    0.860153 +- 0.0646898      6      bad
chromium@469662                    0.887033 +- 0.0554191      6      bad
chromium@469710                    0.865057 +- 0.071639       6      bad

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

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979951823335428736

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6464276178403328


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
►

Sign in to add a comment