Issue metadata
Sign in to add a comment
|
6.2%-83.6% regression in media.tough_video_cases_tbmv2 at 465976:466205 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981591652644422944
,
Apr 22 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_pro_perf_bisect Benchmark : media.tough_video_cases_tbmv2 Metric : cpu_time_percentage_avg/video.html?src_crowd2160.mp4 Revision Result N chromium@466068 0.417894 +- 0.0640076 21 good chromium@466205 0.419029 +- 0.0837626 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.crowd2160.mp4 media.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981591652644422944 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5802037704392704 | 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 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981578458846273504
,
Apr 22 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_pro_perf_bisect Benchmark : media.tough_video_cases_tbmv2 Metric : cpu_time_percentage_avg/video.html?src_crowd2160.mp4 Revision Result N chromium@466068 0.410303 +- 0.0657762 21 good chromium@466205 0.414022 +- 0.0495363 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.crowd2160.mp4 media.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981578458846273504 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5802037704392704 | 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 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981481332674018224
,
Apr 24 2017
=== BISECT JOB RESULTS === Perf regression found but unable to continue Bisect was stopped because a commit couldn't be classified as either good or bad. Bisect Details Configuration: mac_retina_perf_bisect Benchmark : media.tough_video_cases_tbmv2 Metric : cpu_time_percentage_avg/video.html?src_crowd2160.mp4 Revision Result N chromium@465975 0.28967 +- 0.0153834 21 good chromium@466088 0.28985 +- 0.0169124 21 unknown chromium@466200 0.292808 +- 0.0192934 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.crowd2160.mp4 media.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981481332674018224 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5802037704392704 | 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 24 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981406534891448000
,
Apr 24 2017
Trying again with a slightly bigger range
,
Apr 25 2017
=== Auto-CCing suspected CL author crouleau@chromium.org === Hi crouleau@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : crouleau Commit : 597f6ab23b8535ca35d128e25bb0f57398e6da37 Date : Thu Apr 20 22:08:10 2017 Subject: Remove legacy codecs coverage from tough_video_cases pageset. Bisect Details Configuration: mac_10_12_perf_bisect Benchmark : media.tough_video_cases_tbmv2 Metric : cpu_time_percentage_avg/cpu_time_percentage_avg Change : 5.71% | 0.281246206092 -> 0.29730551557 Revision Result N chromium@465602 0.281246 +- 0.00364247 6 good chromium@465889 0.284822 +- 0.00602624 6 good chromium@466032 0.286574 +- 0.00235562 6 good chromium@466104 0.287051 +- 0.00648191 6 good chromium@466140 0.284916 +- 0.0080917 6 good chromium@466149 0.286467 +- 0.00397497 6 good chromium@466154 0.284206 +- 0.00401105 6 good chromium@466155 0.285864 +- 0.00527322 6 good chromium@466156 0.29466 +- 0.00640979 6 bad <-- chromium@466158 0.297096 +- 0.00555829 6 bad chromium@466175 0.297306 +- 0.007719 6 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests media.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981406534891448000 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4616773833326592 | 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 25 2017
Ah, this is helpful. in https://codereview.chromium.org/2830953004 , I deleted "crowd2160.mp4" media, but I didn't delete Page12 which uses it. Because of issue 713394 , I think that the playback is failing for Page12 but no error is being thrown. Since playback is failing, cpu usage is really different.
,
May 1 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by zhanliang@google.com
, Apr 22 2017