Issue metadata
Sign in to add a comment
|
8.1% regression in v8.infinite_scroll_tbmv2 at 459722:459794 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983350597693248640
,
Apr 4 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: a6cc18bb2df8ec78c36fe98da46b06d0837c9a6b bad_revision : 0dfbac01cd2072259a4d6e8e7e0b97fb7b7d9e1e If failures persist contact the team (see below) and report the error. Bisect Details Configuration: win_x64_perf_bisect Benchmark : v8.infinite_scroll_tbmv2 Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max Revision Result N chromium@459721 38637340 +- 1719593 6 good chromium@459758 39262230 +- 1674897 6 good chromium@459776 39597323 +- 1184079 6 good chromium@459785 39313082 +- 3182542 14 good chromium@459790 --- --- build failure chromium@459794 42957846 +- 4324803 14 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983350597693248640 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5025077839527936 | 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!
,
Apr 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982659706122881056
,
Apr 12 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: a6cc18bb2df8ec78c36fe98da46b06d0837c9a6b bad_revision : 0dfbac01cd2072259a4d6e8e7e0b97fb7b7d9e1e If failures persist contact the team (see below) and report the error. Bisect Details Configuration: win_x64_perf_bisect Benchmark : v8.infinite_scroll_tbmv2 Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_max Revision Result N chromium@459721 39350091 +- 1350154 6 good chromium@459758 38045432 +- 4396588 6 good chromium@459776 39268703 +- 2376891 6 good chromium@459785 39027768 +- 2579244 14 good chromium@459790 --- --- build failure chromium@459794 42754777 +- 3324174 14 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982659706122881056 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5025077839527936 | 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!
,
Apr 27 2017
Reference build also regressed by the same amount. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ulan@google.com
, Apr 3 2017