New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 726922 link

Starred by 1 user
Status: Duplicate
Merged: issue 726902
Owner: ----
Closed: Jun 2017
Cc:
█ briander...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-2.1% regression in memory.top_10_mobile at 474338:474465

Project Member Reported by briander...@chromium.org, May 26 2017 
See the link to graphs below.
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 28 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: acd48bf956b4bf7de6702c20ebdbe83132a2be8c
  bad_revision : 90089e1929d8ec7bda755456e7a54808a2c843ea

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


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_https_m_facebook_com_rihanna

Revision             Result                   N
chromium@474350      53005293 +- 1697807      14       good
chromium@474381      52452623 +- 6045294      21       good
chromium@474395      ---                      ---      build failure
chromium@474396      53667577 +- 1006633      9        bad
chromium@474408      53428644 +- 1057974      14       bad
chromium@474465      53363107 +- 2466684      9        bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 memory.top_10_mobile

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

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


| 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 28 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: acd48bf956b4bf7de6702c20ebdbe83132a2be8c
  bad_revision : 90089e1929d8ec7bda755456e7a54808a2c843ea

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


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_https_m_facebook_com_rihanna

Revision             Result                   N
chromium@474350      53005293 +- 1697807      14       good
chromium@474381      52452623 +- 6045294      21       good
chromium@474395      ---                      ---      build failure
chromium@474396      53667577 +- 1006633      9        bad
chromium@474408      53428644 +- 1057974      14       bad
chromium@474465      53363107 +- 2466684      9        bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 memory.top_10_mobile

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

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


| 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, Jun 13 2017

Mergedinto: 726902
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : fdoray
  Commit : b87bcfb8c3b17bbcad020186a94e935e2fd0d162
  Date   : Wed May 24 17:49:40 2017
  Subject: [reland] Use TaskScheduler instead of WorkerPool in v8_platform.cc.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/foreground/http_www_baidu_com_s_word_google
  Change       : 1.87% | 42302208.0 -> 43173579.5556

Revision             Result                   N
chromium@474300      42302208 +- 957572       9       good
chromium@474325      42367209 +- 1051753      6       good
chromium@474338      42440511 +- 972392       9       good
chromium@474344      42398920 +- 636335       6       good
chromium@474345      42268789 +- 910560       6       good
chromium@474346      43197226 +- 1127369      9       bad       <--
chromium@474347      43323437 +- 546462       6       bad
chromium@474350      43068214 +- 1915651      14      bad
chromium@474400      43173580 +- 813339       9       bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 memory.top_10_mobile

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

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


| 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, Jun 13 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: dcc19bd2a57be365678a394563d58994a58ef555
  bad_revision : c1878a272a87bd797949717bebdfdbc1e6f0c143

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


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/background/after_http_www_baidu_com_s_word_google

Revision             Result                  N
chromium@474000      40945555 +- 755659      6      good
chromium@474300      41087349 +- 778725      6      good
chromium@474375      42155545 +- 765038      6      bad
chromium@474450      42032564 +- 634090      6      bad
chromium@474600      41731745 +- 303035      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 memory.top_10_mobile

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

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


| 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, Jun 15 2017 


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

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: dcc19bd2a57be365678a394563d58994a58ef555
  bad_revision : c1878a272a87bd797949717bebdfdbc1e6f0c143

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


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/background/after_http_www_baidu_com_s_word_google

Revision             Result                  N
chromium@474000      40945555 +- 755659      6      good
chromium@474300      41087349 +- 778725      6      good
chromium@474375      42155545 +- 765038      6      bad
chromium@474450      42032564 +- 634090      6      bad
chromium@474600      41731745 +- 303035      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 memory.top_10_mobile

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

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


| 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