Issue metadata
Sign in to add a comment
|
123.2% regression in memory.top_10_mobile at 468688:468774 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980446453211885840
,
May 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980446442392572624
,
May 5 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background/after_https_m_facebook_com_rihanna Revision Result N chromium@468687 11487963 +- 4689110 21 good chromium@468774 12489728 +- 3364958 21 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/8980446442392572624 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5865345069350912 | 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 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980428151809073040
,
May 5 2017
=== Auto-CCing suspected CL author mtrofin@chromium.org === Hi mtrofin@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : mtrofin Commit : b6567be47346a26d9e431c64d02e9176ae6a6308 Date : Tue May 02 19:30:05 2017 Subject: [wasm] Ensure postMessage doesn't work cross process. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background/after_https_m_facebook_com_rihanna Change : 8.88% | 11288137.1429 -> 12291072.0 Revision Result N chromium@468687 11288137 +- 4360185 21 good chromium@468731 11385710 +- 4550739 21 good chromium@468737 12786005 +- 14238.1 6 good chromium@468740 12786119 +- 19702.9 9 good chromium@468741 12782592 +- 19961.4 6 good chromium@468742 12803243 +- 17463.1 6 bad <-- chromium@468753 12788736 +- 39500.4 14 bad chromium@468774 12291072 +- 4082964 21 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/8980446453211885840 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5821736873885696 | 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 5 2017
That CL is a test, and does not impact production code.
,
May 6 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background/after_https_m_facebook_com_rihanna Revision Result N chromium@468687 11287357 +- 4358494 21 good chromium@468774 12287464 +- 4099930 21 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/8980428151809073040 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5865345069350912 | 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 kraynov@chromium.org
, May 5 2017