New issue
Advanced search Search tips

Issue 718803 link

Starred by 1 user

Issue metadata

Status: WontFix
Merged: issue 719032
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.9%-409.6% regression in v8.runtimestats.browsing_mobile_classic at 468327:469224

Project Member Reported by verwa...@chromium.org, May 5 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=718803

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8rWX5QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8rXD-AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiurn8QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8rmh9ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgivTksgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8uvBugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8rWX5QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8oDbkAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8o7bgAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8q3WuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8r-EzAgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8qe_5gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8vjz2AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8uG_4wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgirqMoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8pmRoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgit7ZtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8qbExQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgisK_oAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiu6UtQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8vjz2AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8qmxuQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8oWvzwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8oWvjwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8sqn9wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8t6prgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgivzNsAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8oWvjwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8s3apAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgitjr1wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8peLowsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgspa77gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8qzT2goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8v6JugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgspWDwQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8t7i5ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8se5xQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgioC46AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8unuswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8uytsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgisCTjwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8oaAjAgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8oL9iAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8vXfugkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgioT29wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgioT29wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8r3_iwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8v6WqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgitjrlwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8qecgwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsomx4AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8snFtgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8qT8mQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8smq-ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8snepwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8v3kqgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8rzk4AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8oau4wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8pe6tAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8rShvgsM


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

android-nexus5
android-nexus5X
android-nexus6
android-webview-nexus5X
android-webview-nexus6

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : V8 C++:duration_avg/browse_chrome/browse_chrome_newtab


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.runtimestats.browsing_mobile

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

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


| 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!

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : V8 C++:duration_avg/browse_chrome/browse_chrome_newtab

Revision             Result                  N
chromium@468624      3359.64 +- 742.745      21      good
chromium@469150      3369.1 +- 674.017       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.runtimestats.browsing_mobile

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

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


| 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!
Owner: tebbi@chromium.org
Status: Assigned (was: Untriaged)
Project Member

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


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : JavaScript:duration_avg/browse_shopping/browse_shopping_avito

Revision             Result                  N
chromium@468624      8579.52 +- 2755.71      21      good
chromium@469150      8751.55 +- 3127.11      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.avito v8.runtimestats.browsing_mobile

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

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


| 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 12 by 42576172...@developer.gserviceaccount.com, May 20 2017


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : JavaScript:duration_avg/browse_shopping/browse_shopping_avito

Revision             Result                  N
chromium@468624      9584.01 +- 3044.74      21      good
chromium@469150      9809.7 +- 2764.04       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.avito v8.runtimestats.browsing_mobile

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

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


| 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 13 by 42576172...@developer.gserviceaccount.com, May 20 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: 03499255747e2689aac736e866ed3520e13df725
  bad_revision : 201ab5f17e23e13c6797cfe3215dca8808bb6313

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


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : API:duration_avg/browse_news/browse_news_reddit

Revision             Result                  N
chromium@468624      141.417 +- 12.0685      14      good
chromium@468875      141.043 +- 2.10953      3       good
chromium@469027      141.198 +- 2.89754      3       good
chromium@469150      145.694 +- 6.5977       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.news.reddit v8.runtimestats.browsing_mobile

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

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


| 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 14 by 42576172...@developer.gserviceaccount.com, May 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: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Parse:duration_avg/browse_news/browse_news_qq

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/v8/v8.git/+log/c2f4498f4680fee60606d176aacfaf2c81b66aa0..00912d73f1a83f16b6e7f88bf4837d5a7a8dc857


Revision                           Result                  N
chromium@468643                    223.066 +- 7.77931      14       good
chromium@468643,v8@c2f4498f46      221.463 +- 10.503       14       good
chromium@468643,v8@8f4e8c0aee      ---                     ---      build failure
chromium@468643,v8@34e7945647      ---                     ---      build failure
chromium@468643,v8@a39a833ad3      ---                     ---      build failure
chromium@468643,v8@00912d73f1      246.184 +- 2.80231      3        bad
chromium@468643,v8@b8e9bd4051      249.775 +- 3.86428      3        bad
chromium@468644                    253.126 +- 1.58041      5        bad
chromium@468645                    252.027 +- 2.22006      3        bad
chromium@468647                    243.327 +- 1.87782      3        bad
chromium@468651                    245.509 +- 4.93197      3        bad
chromium@468659                    245.788 +- 5.01021      3        bad
chromium@468675                    249.534 +- 3.83517      3        bad
chromium@468706                    251.495 +- 6.67668      5        bad
chromium@468768                    251.116 +- 5.98286      4        bad
chromium@468893                    251.148 +- 5.91263      5        bad
chromium@469142                    249.71 +- 6.05565       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.news.qq v8.runtimestats.browsing_mobile

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

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


| 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 16 by 42576172...@developer.gserviceaccount.com, May 21 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: 5bd9e2fd296b774e34d04cddfb09893525a79c04
  bad_revision : 3f7bc3a7fd2911e29e1c1330bc2b815eeed8cb6c

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


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : API:duration_avg/browse_news/browse_news_reddit

Revision             Result                    N
chromium@468624      141.18 +- 5.98341         14      good
chromium@468746      145.281 +- 3.00302        3       bad
chromium@468893      10255938 +- 25121459      3       bad
chromium@469150      143.796 +- 6.18563        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.news.reddit v8.runtimestats.browsing_mobile

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

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


| 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!

Comment 17 by tebbi@chromium.org, May 22 2017

Mergedinto: 719032
Status: Duplicate (was: Assigned)

Comment 18 by tebbi@chromium.org, May 22 2017

Status: Assigned (was: Duplicate)

Comment 19 by tebbi@chromium.org, May 24 2017

Cc: tebbi@chromium.org
 Issue 718804  has been merged into this issue.

Comment 20 by tebbi@chromium.org, May 24 2017

 Issue 718805  has been merged into this issue.
Project Member

Comment 22 by 42576172...@developer.gserviceaccount.com, Jun 26 2017


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : JavaScript:duration_avg/browse_shopping/browse_shopping_avito

Revision             Result                  N
chromium@468624      10736.2 +- 4596.55      21      good
chromium@469150      10910.5 +- 2865.18      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.avito v8.runtimestats.browsing_mobile

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

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


| 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 24 by 42576172...@developer.gserviceaccount.com, Jun 26 2017


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : JavaScript:duration_avg/browse_shopping/browse_shopping_avito

Revision             Result                  N
chromium@468624      8421.33 +- 1932.23      21      good
chromium@469150      8476.14 +- 1917.77      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.avito v8.runtimestats.browsing_mobile

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

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


| 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!

Comment 25 by tebbi@chromium.org, Aug 29 2017

Status: WontFix (was: Assigned)
not reproducible

Sign in to add a comment