Issue metadata
Sign in to add a comment
|
2.3%-130.7% regression in loading.desktop at 471646:471725 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 18 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979249512460035520
,
May 18 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Yutaka Hirano Commit : f20d10a747ef558a18cdd6925df977352e477997 Date : Mon May 15 04:44:45 2017 Subject: Revert "Set URLResponseBodyConsumer::kMaxNumConsumedBytesInTask to 32K" Bisect Details Configuration: winx64ati_perf_bisect Benchmark : loading.desktop Metric : timeToFirstMeaningfulPaint_avg/pcv1-cold/Daum Change : 55.55% | 1497.99871429 -> 2330.18877778 Revision Result N chromium@471654 1498.0 +- 2435.91 14 good chromium@471666 1448.81 +- 2391.19 14 good chromium@471669 1497.63 +- 2465.73 14 good chromium@471670 2336.41 +- 126.537 6 bad <-- chromium@471671 2246.58 +- 1552.45 14 bad chromium@471672 2115.02 +- 2317.51 21 bad chromium@471677 2271.34 +- 654.251 14 bad chromium@471700 2330.19 +- 223.838 9 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 --story-filter=Daum loading.desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979249512460035520 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6443129068060672 | 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