Issue metadata
Sign in to add a comment
|
1.2%-1.4% regression in memory.top_10_mobile at 441034:441036 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8990941524366436144
,
Jan 9 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus9_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg Revision Result N chromium@441033 8518413 +- 38597455 120 good chromium@441036 8555415 +- 38292388 120 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8990941524366436144 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5791162641678336 | 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!
,
Jan 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8990933195586496672
,
Jan 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8990933165804157888
,
Jan 9 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/background Revision Result N chromium@441033 5560007 +- 3870695 60 good chromium@441036 5676144 +- 4288578 60 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8990933195586496672 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5791016075919360 | 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!
,
Jan 9 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus9_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/background Revision Result N chromium@441033 5768352 +- 4505953 60 good chromium@441036 5826742 +- 4646551 60 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8990933165804157888 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5825152610205696 | 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!
,
Jan 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8990672543020589456
,
Jan 12 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/background Change : 1.75% | 5560702.4 -> 5658180.13333 Revision Result N chromium@441033 5560702 +- 3874787 60 good chromium@441036 5658180 +- 3789379 60 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/None Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5778317602455552 | 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!
,
Jan 12 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/background Revision Result N chromium@441033 5565974 +- 3915982 60 good chromium@441036 5661634 +- 3959319 60 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8990672543020589456 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5599063518478336 | 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!
,
Jan 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8990298254418899056
,
Jan 17 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 : memory.top_10_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/background Change : 0.84% | 5522828.11429 -> 5572415.33333 Suspected Commit Range 4 commits in range https://chromium.googlesource.com/v8/v8.git/+log/350d8e345ec690997521b30a5f2ea73e98e0bd24..5668ce39873f97f0bd8b25289f41c88cf91aa9bc Revision Result N chromium@441023 5522828 +- 59171.5 14 good chromium@441023,v8@350d8e345e 5539098 +- 55487.2 14 good chromium@441023,v8@f2e8c9786f --- --- build failure chromium@441023,v8@05873add85 --- --- build failure chromium@441023,v8@26c293a93b --- --- build failure chromium@441023,v8@5668ce3987 5564028 +- 78768.8 14 bad chromium@441023,v8@7ad54344c1 5567543 +- 94686.4 14 bad chromium@441024 5558570 +- 41729.8 14 bad chromium@441025 5575640 +- 68012.8 9 bad chromium@441026 5572415 +- 61713.4 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-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/8990298254418899056 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5832301113507840 | 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!
,
Jan 17 2017
mvstanton@ FYI: Looks like this is due to builtin ports. Closing since code-size increases seem to be expected. 05873ad [builtins] More stubs to the builtin-o-sphere. by mvstanton · 3 weeks ago f2e8c97 [builtins] FastNewFunctionContextStub becomes a builtin by mvstanton · 3 weeks ago
,
Jan 17 2017
Thanks, I think that makes good sense..
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982611850835587856
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982584576644437504
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982584567650770544
,
Apr 11 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus9_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg Revision Result N chromium@441033 8518413 +- 38597455 120 good chromium@441036 8555415 +- 38292388 120 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/8982584567650770544 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5791162641678336 | 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 jgruber@chromium.org
, Jan 9 2017