Issue metadata
Sign in to add a comment
|
26.9%-241.2% regression in thread_times.tough_scrolling_cases at 401916:401961 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 28 2016
=== Auto-CCing suspected CL author ericrk@chromium.org === Hi ericrk@chromium.org, the bisect results pointed to your CL below as possibly causing a regression. Please have a look at this info and see whether your CL be related. ===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : This change blacklists GPU rasterization for all GPUs on MacOS that have not had test coverage. Author : ericrk Commit description: The GPUs which are not blacklisted are those from the following GPU series: Intel: 6th and 7th Generation GPUs NVidia: Geforce 7XX GPUs NVidia: Geforce 6XX GPUs ATI: R300 Series GPUs ATI: R200 Series GPUs ATI: HD 7XXX series GPUs This gives us roughly 70% GPU Raster enablement on Mac. BUG= 614468 , 613272 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2066733003 Cr-Commit-Position: refs/heads/master@{#401933} Commit : 5033c4f6e97a466f03132ed2cbb655a8807e415c Date : Fri Jun 24 19:37:23 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@401915 0.961726 0.00600427 5 good chromium@401927 0.973033 0.00614288 5 good chromium@401930 0.968233 0.0112048 5 good chromium@401932 0.966079 0.0146266 5 good chromium@401933 3.14765 0.0422776 5 bad <-- chromium@401938 3.16717 0.0260303 5 bad chromium@401961 3.17569 0.0225025 5 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 623668 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases Test Metric: thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame Relative Change: 230.21% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/609 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008675233171258736 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5345776348168192 | 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!
,
Jun 28 2016
,
Jun 28 2016
This change was needed to address performance regressions due to GPU raster on this bot's GPU. The increased CPU usage comes with better performance, and this just restores levels to M52's original performance.
,
Jul 22 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006405793288151952
,
Jul 22 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006405785807463872
,
Jul 22 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006405059725722448
,
Jul 22 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006405052202947328
,
Jul 23 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : This change blacklists GPU rasterization for all GPUs on MacOS that have not had test coverage. Author : ericrk Commit description: The GPUs which are not blacklisted are those from the following GPU series: Intel: 6th and 7th Generation GPUs NVidia: Geforce 7XX GPUs NVidia: Geforce 6XX GPUs ATI: R300 Series GPUs ATI: R200 Series GPUs ATI: HD 7XXX series GPUs This gives us roughly 70% GPU Raster enablement on Mac. BUG= 614468 , 613272 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2066733003 Cr-Commit-Position: refs/heads/master@{#401933} Commit : 5033c4f6e97a466f03132ed2cbb655a8807e415c Date : Fri Jun 24 19:37:23 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@401915 0.965451 0.00848282 5 good chromium@401927 0.973936 0.00947259 5 good chromium@401930 0.966667 0.00740646 5 good chromium@401932 0.961564 0.0072634 5 good chromium@401933 3.18368 0.020272 5 bad <-- chromium@401938 3.14516 0.0511735 5 bad chromium@401961 3.14431 0.0644799 5 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 623668 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases Test Metric: thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame Relative Change: 225.68% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/658 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006405059725722448 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6356291539173376 | 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!
,
Jul 23 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : This change blacklists GPU rasterization for all GPUs on MacOS that have not had test coverage. Author : ericrk Commit description: The GPUs which are not blacklisted are those from the following GPU series: Intel: 6th and 7th Generation GPUs NVidia: Geforce 7XX GPUs NVidia: Geforce 6XX GPUs ATI: R300 Series GPUs ATI: R200 Series GPUs ATI: HD 7XXX series GPUs This gives us roughly 70% GPU Raster enablement on Mac. BUG= 614468 , 613272 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2066733003 Cr-Commit-Position: refs/heads/master@{#401933} Commit : 5033c4f6e97a466f03132ed2cbb655a8807e415c Date : Fri Jun 24 19:37:23 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@401915 10.0924 0.0866006 5 good chromium@401927 10.1792 0.0702199 5 good chromium@401930 10.1941 0.0620245 5 good chromium@401932 10.1581 0.0695183 5 good chromium@401933 12.3285 0.0405847 5 bad <-- chromium@401938 12.2498 0.038692 5 bad chromium@401961 12.3358 0.0375479 5 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 623668 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases Test Metric: thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame Relative Change: 22.23% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/657 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006405785807463872 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5901078021799936 | 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!
,
Jul 29 2016
Bisect failed: Unknown Failure reason: the build has failed. Additional errors: The metric was not found in the test output. Either of the initial "good" or "bad" revisions failed to be tested or built.
,
Jul 29 2016
Bisect failed: Unknown Failure reason: the build has failed. Additional errors: The metric was not found in the test output. Either of the initial "good" or "bad" revisions failed to be tested or built.
,
Jul 29 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005837437709471552
,
Jul 29 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005837434827666128
,
Jul 29 2016
Bisect failed: Unknown Failure reason: the build has failed. Additional errors: The metric was not found in the test output. Either of the initial "good" or "bad" revisions failed to be tested or built.
,
Jul 29 2016
Bisect failed: Unknown Failure reason: the build has failed. Additional errors: The metric was not found in the test output. Either of the initial "good" or "bad" revisions failed to be tested or built.
,
Jul 30 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005743004593143296
,
Jul 30 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005743003216012992
,
Jul 30 2016
=== Auto-CCing suspected CL author ericrk@chromium.org === Hi ericrk@chromium.org, the bisect results pointed to your CL below as possibly causing a regression. Please have a look at this info and see whether your CL be related. ===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : This change blacklists GPU rasterization for all GPUs on MacOS that have not had test coverage. Author : ericrk Commit description: The GPUs which are not blacklisted are those from the following GPU series: Intel: 6th and 7th Generation GPUs NVidia: Geforce 7XX GPUs NVidia: Geforce 6XX GPUs ATI: R300 Series GPUs ATI: R200 Series GPUs ATI: HD 7XXX series GPUs This gives us roughly 70% GPU Raster enablement on Mac. BUG= 614468 , 613272 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2066733003 Cr-Commit-Position: refs/heads/master@{#401933} Commit : 5033c4f6e97a466f03132ed2cbb655a8807e415c Date : Fri Jun 24 19:37:23 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@401915 10.0625 0.0479765 5 good chromium@401927 10.1797 0.0409663 5 good chromium@401930 10.1886 0.0442402 5 good chromium@401932 10.1542 0.0737873 5 good chromium@401933 12.3599 0.080428 5 bad <-- chromium@401938 12.3279 0.0596113 5 bad chromium@401961 12.2752 0.0782519 5 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 623668 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases Test Metric: thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame Relative Change: 21.99% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/678 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005837434827666128 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5826259154632704 | 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!
,
Jul 30 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : This change blacklists GPU rasterization for all GPUs on MacOS that have not had test coverage. Author : ericrk Commit description: The GPUs which are not blacklisted are those from the following GPU series: Intel: 6th and 7th Generation GPUs NVidia: Geforce 7XX GPUs NVidia: Geforce 6XX GPUs ATI: R300 Series GPUs ATI: R200 Series GPUs ATI: HD 7XXX series GPUs This gives us roughly 70% GPU Raster enablement on Mac. BUG= 614468 , 613272 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2066733003 Cr-Commit-Position: refs/heads/master@{#401933} Commit : 5033c4f6e97a466f03132ed2cbb655a8807e415c Date : Fri Jun 24 19:37:23 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@401928 10.2089 0.0947467 5 good chromium@401931 10.1584 0.0611081 5 good chromium@401932 10.1767 0.0441279 5 good chromium@401933 12.3454 0.121714 5 bad <-- chromium@401934 12.2769 0.0749945 5 bad chromium@401939 12.3219 0.0793042 5 bad chromium@401950 12.3295 0.0416407 5 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 623668 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.tough_scrolling_cases Test Metric: thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame Relative Change: 20.77% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/685 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005837437709471552 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5814444907560960 | 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! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by lanwei@google.com
, Jun 27 2016