Issue metadata
Sign in to add a comment
|
5.1% regression in thread_times.key_mobile_sites_smooth at 467897:467961 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980421331059023056
,
May 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980421324284603584
,
May 6 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : nednguyen Commit : e80a730b1b1b43ec5fa205dd99e5f00693173f4c Date : Fri Apr 28 09:26:12 2017 Subject: [Telemetry] Switch Android platform to no longer uses test ca Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : thread_times.key_mobile_sites_smooth Metric : thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame Change : 5.44% | 2.60780942386 -> 2.74980167213 Revision Result N chromium@467896 2.60781 +- 0.0834943 6 good chromium@467929 2.59462 +- 0.0498291 6 good chromium@467945 2.62267 +- 0.0607492 6 good chromium@467953 2.61897 +- 0.1052 6 good chromium@467953,catapult@e80a730b1b 2.80634 +- 0.0854759 6 bad <-- chromium@467954 2.77794 +- 0.0598712 6 bad chromium@467955 2.80622 +- 0.0268029 6 bad chromium@467957 2.82319 +- 0.0857702 6 bad chromium@467961 2.7498 +- 0.106089 6 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 thread_times.key_mobile_sites_smooth Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980421324284603584 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5256416417284096 | 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 6 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : nednguyen Commit : e80a730b1b1b43ec5fa205dd99e5f00693173f4c Date : Fri Apr 28 09:26:12 2017 Subject: [Telemetry] Switch Android platform to no longer uses test ca Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : thread_times.key_mobile_sites_smooth Metric : thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame Change : 7.81% | 2.62579402995 -> 2.83081802181 Revision Result N chromium@467896 2.62579 +- 0.1125 6 good chromium@467929 2.64812 +- 0.050154 6 good chromium@467945 2.58985 +- 0.0772783 6 good chromium@467953 2.63232 +- 0.0383203 6 good chromium@467953,catapult@e80a730b1b 2.78482 +- 0.0873918 6 bad <-- chromium@467954 2.80751 +- 0.0684627 6 bad chromium@467955 2.73037 +- 0.133694 6 bad chromium@467957 2.78589 +- 0.127417 6 bad chromium@467961 2.83082 +- 0.120036 6 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 thread_times.key_mobile_sites_smooth Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980421331059023056 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6426007952687104 | 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