New issue
Advanced search Search tips

Issue 715103 link

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



Sign in to add a comment

213.7% regression in v8.runtimestats.browsing_mobile at 466767:466806

Project Member Reported by jgruber@chromium.org, Apr 25 2017 
No interesting V8 change in this range at first glance.

Comment 1 by jgruber@chromium.org, Apr 25 2017 

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkonaoAoM


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

android-webview-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 26 2017 


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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_news/browse_news_qq

Revision             Result                  N
chromium@466766      10.7571 +- 20.5497      21      good
chromium@466806      10.1556 +- 21.9942      21      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/8981332032018047008

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


| 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, Apr 26 2017

Mergedinto: 715279
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : skobes
  Commit : 8a4d4531daca4b9a1f6dc1224bcb7134dc053ff4
  Date   : Mon Apr 24 19:19:10 2017
  Subject: Temporarily ignore ScrollbarAnimationController::DidRequestShowFromMainThread.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-full-mark-compactor_avg/browse_news/browse_news_toi
  Change       : 5.23% | 54.0771111111 -> 56.9045555556

Revision             Result                  N
chromium@466562      54.0771 +- 4.70193      9       good
chromium@466679      54.5505 +- 5.7355       14      good
chromium@466709      52.8611 +- 14.0744      14      good
chromium@466711      53.8879 +- 7.09759      14      good
chromium@466712      57.7755 +- 5.37046      6       bad       <--
chromium@466713      57.4158 +- 6.68413      9       bad
chromium@466717      56.3986 +- 8.23988      14      bad
chromium@466724      56.261 +- 11.385        14      bad
chromium@466738      56.662 +- 4.02482       9       bad
chromium@466796      56.9046 +- 3.69436      9       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.toi v8.runtimestats.browsing_mobile

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

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


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


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

Suspected Commit
  Author : skobes
  Commit : 8a4d4531daca4b9a1f6dc1224bcb7134dc053ff4
  Date   : Mon Apr 24 19:19:10 2017
  Subject: Temporarily ignore ScrollbarAnimationController::DidRequestShowFromMainThread.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-full-mark-compactor_sum/browse_news/browse_news_toi
  Change       : 7.92% | 53.6152222222 -> 57.8608333333

Revision             Result                  N
chromium@466562      53.6152 +- 5.89069      9       good
chromium@466679      54.1663 +- 3.2536       6       good
chromium@466709      53.9026 +- 6.33768      14      good
chromium@466711      53.5314 +- 5.05887      9       good
chromium@466712      56.8427 +- 6.69323      9       bad       <--
chromium@466713      56.2588 +- 11.0504      21      bad
chromium@466717      56.4743 +- 12.1768      21      bad
chromium@466724      56.5069 +- 6.93593      14      bad
chromium@466738      57.4848 +- 4.33654      9       bad
chromium@466796      57.8608 +- 3.56034      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.news.toi v8.runtimestats.browsing_mobile

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

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


| 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, Apr 26 2017 


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

Suspected Commit
  Author : skobes
  Commit : 8a4d4531daca4b9a1f6dc1224bcb7134dc053ff4
  Date   : Mon Apr 24 19:19:10 2017
  Subject: Temporarily ignore ScrollbarAnimationController::DidRequestShowFromMainThread.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-full-mark-compactor_max/browse_news/browse_news_toi
  Change       : 5.19% | 54.3618571429 -> 57.1812857143

Revision             Result                  N
chromium@466562      54.3619 +- 7.0469       14      good
chromium@466679      54.2293 +- 5.50732      14      good
chromium@466709      54.6769 +- 5.02696      14      good
chromium@466711      54.2029 +- 7.25018      14      good
chromium@466712      56.601 +- 11.1058       21      bad       <--
chromium@466713      56.8051 +- 12.1116      21      bad
chromium@466717      56.8949 +- 8.42204      14      bad
chromium@466724      56.1324 +- 4.38333      9       bad
chromium@466738      56.7026 +- 8.37919      14      bad
chromium@466796      57.1813 +- 10.0626      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.toi v8.runtimestats.browsing_mobile

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

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


| 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, Apr 28 2017 


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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_news/browse_news_qq

Revision             Result                  N
chromium@466766      10.7571 +- 20.5497      21      good
chromium@466806      10.1556 +- 21.9942      21      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/8981286034661879824

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


| 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