Issue metadata
Sign in to add a comment
|
4.7% regression in memory.top_10_mobile at 470468:470540 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 18 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979256326169495696
,
May 19 2017
=== BISECT JOB RESULTS ===
Bisect failed unexpectedly
Bisect was aborted with the following:
Step('Check bisect finished on revision chromium@470539,skia@ca572f9c90.fetch file ca572f9c90e1187913423901bff783f3462478b9:DEPS') failed with return_code 1
Bisect Details
Configuration: android_nexus5X_perf_bisect
Benchmark : memory.top_10_mobile
Metric : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/background/after_http_yandex_ru_touchsearch_text_science
Revision Result N
chromium@470467 260496 +- 0.0 14 good
chromium@470504 197249 +- 231833 14 good
chromium@470522 190345 +- 229572 14 good
chromium@470531 190459 +- 229255 14 good
chromium@470536 189002 +- 226982 14 good
chromium@470538 181478 +- 264269 21 good
chromium@470539 189799 +- 231248 14 good
chromium@470539,skia@ca572f9c90 182779 +- 263292 20 good
chromium@470540 263544 +- 122985 14 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/8979256326169495696
Is this bisect wrong?
https://chromeperf.appspot.com/bad_bisect?try_job_id=5270666615455744
| 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!
,
May 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979193770477329712
,
May 19 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : yhirano Commit : 91088a195969f5af61f404c9f02edc622cbe373a Date : Wed May 10 05:49:31 2017 Subject: Add Field Trial Testing Configuration for MojoLoading Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/background/after_http_yandex_ru_touchsearch_text_science Change : 1.29% | 260496.0 -> 257127.555556 Revision Result N chromium@470467 260496 +- 0.0 14 good chromium@470486 260496 +- 0.0 14 good chromium@470488 260496 +- 0.0 9 good chromium@470489 260496 +- 0.0 9 good chromium@470490 258479 +- 120329 9 bad <-- chromium@470496 263544 +- 122985 14 bad chromium@470504 262548 +- 124346 14 bad chromium@470540 257128 +- 119439 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/8979193770477329712 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5270666615455744 | 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 |
|||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, May 18 2017