New issue
Advanced search Search tips

Issue 683193 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

36.7%-44.6% regression in v8.key_mobile_sites_smooth at 444622:444710

Project Member Reported by mustaq@chromium.org, Jan 20 2017

Issue description

See the link to graphs below.
 

Comment 1 by mustaq@chromium.org, Jan 20 2017

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

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


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

android-nexus5X
android-nexus9
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 21 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_nexus5X_perf_bisect
  Benchmark    : v8.key_mobile_sites_smooth
  Metric       : v8_gc_total_percentage_idle/v8_gc_total_percentage_idle

Suspected Commit Range
  10 commits in range
  https://chromium.googlesource.com/chromium/src/+log/1fdab380fd5cc1c9485703b0bfbc128cb2557c62..3b6cc5bcfd2a9275549e49b8ecc6d6b8b8bb9773


Revision             Result                  N
chromium@444621      17.5094 +- 4.28425      6        good
chromium@444631      18.2964 +- 2.86552      6        good
chromium@444632      ---                     ---      build failure
chromium@444633      ---                     ---      build failure
chromium@444634      ---                     ---      build failure
chromium@444635      ---                     ---      build failure
chromium@444636      ---                     ---      build failure
chromium@444637      ---                     ---      build failure
chromium@444638      ---                     ---      build failure
chromium@444639      ---                     ---      build failure
chromium@444640      ---                     ---      build failure
chromium@444641      11.0993 +- 2.40867      6        bad
chromium@444661      11.6821 +- 3.93893      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 v8.key_mobile_sites_smooth

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

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


| 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 Tests>AutoBisect.  Thank you!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jan 27 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_nexus9_perf_bisect
  Benchmark    : v8.key_mobile_sites_smooth
  Metric       : v8_gc_total_percentage_idle/v8_gc_total_percentage_idle

Suspected Commit Range
  20 commits in range
  https://chromium.googlesource.com/chromium/src/+log/1fdab380fd5cc1c9485703b0bfbc128cb2557c62..8e9dde1be1c2411de2a8d7a7b7c331d46c324a3f


Revision             Result                  N
chromium@444631      17.8564 +- 4.65401      6        good
chromium@444632      ---                     ---      build failure
---                  ---                     ---      too many build failures to list
chromium@444650      ---                     ---      build failure
chromium@444651      10.3575 +- 1.60634      6        bad
chromium@444671      10.0853 +- 2.72712      6        bad
chromium@444710      9.24385 +- 3.15488      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 v8.key_mobile_sites_smooth

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

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


| 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 Tests>AutoBisect.  Thank you!

Comment 6 Deleted

Status: Untriaged (was: WontFix)
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Apr 11 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_nexus9_perf_bisect
  Benchmark    : v8.key_mobile_sites_smooth
  Metric       : v8_gc_total_percentage_idle/v8_gc_total_percentage_idle

Suspected Commit Range
  20 commits in range
  https://chromium.googlesource.com/chromium/src/+log/1fdab380fd5cc1c9485703b0bfbc128cb2557c62..8e9dde1be1c2411de2a8d7a7b7c331d46c324a3f


Revision             Result                  N
chromium@444631      17.8564 +- 4.65401      6        good
chromium@444632      ---                     ---      build failure
---                  ---                     ---      too many build failures to list
chromium@444650      ---                     ---      build failure
chromium@444651      10.3575 +- 1.60634      6        bad
chromium@444671      10.0853 +- 2.72712      6        bad
chromium@444710      9.24385 +- 3.15488      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 v8.key_mobile_sites_smooth

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

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


| 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!
Removed recovered regressions, one last remains.  Starting another bisect.

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Infra Failure: Step('device_status (3)') returned 1


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.key_mobile_sites_smooth
  Metric       : v8_gc_total_percentage_idle/v8_gc_total_percentage_idle

Revision             Result                  N
chromium@444631      19.923 +- 4.8506        14      good
chromium@444710      18.5534 +- 8.67537      10      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 v8.key_mobile_sites_smooth

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

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


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

Comment 14 by 42576172...@developer.gserviceaccount.com, Jul 11 2017


=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Infra Failure: Step('device_status (3)') returned 1


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.key_mobile_sites_smooth
  Metric       : v8_gc_total_percentage_idle/v8_gc_total_percentage_idle

Revision             Result                  N
chromium@444631      19.462 +- 6.81559       14      good
chromium@444710      18.8772 +- 5.16118      10      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 v8.key_mobile_sites_smooth

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

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


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Untriaged)
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. 

Sign in to add a comment