Issue metadata
Sign in to add a comment
|
115.5% regression in media.tough_video_cases at 454421:454537 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 7 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985754546412698224
,
Mar 7 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985754537512641696
,
Mar 8 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : dalecurtis Commit : f4a6dbf44108f1855faf5a78d4fb06c349ebd70d Date : Fri Mar 03 00:27:26 2017 Subject: Replace FFmpegDemuxer thread per element with base::TaskScheduler. Bisect Details Configuration: mac_10_12_perf_bisect Benchmark : media.tough_video_cases Metric : idle_wakeups_renderer/idle_wakeups_renderer Change : 51.40% | 420.955128205 -> 637.33974359 Revision Result N chromium@454420 420.955 +- 12.1361 6 good chromium@454450 417.526 +- 15.9798 6 good chromium@454451 414.083 +- 20.3349 6 good chromium@454452 632.615 +- 33.029 6 bad <-- chromium@454454 627.737 +- 28.7437 6 bad chromium@454458 633.66 +- 27.6985 6 bad chromium@454465 620.859 +- 63.4256 6 bad chromium@454479 635.301 +- 33.2373 6 bad chromium@454537 637.34 +- 27.251 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 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8985754546412698224 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5299531735891968 | 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!
,
Mar 8 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : dalecurtis Commit : f4a6dbf44108f1855faf5a78d4fb06c349ebd70d Date : Fri Mar 03 00:27:26 2017 Subject: Replace FFmpegDemuxer thread per element with base::TaskScheduler. Bisect Details Configuration: mac_10_12_perf_bisect Benchmark : media.tough_video_cases Metric : idle_wakeups_renderer/idle_wakeups_renderer Change : 51.85% | 419.307692308 -> 636.737179487 Revision Result N chromium@454420 419.308 +- 18.081 6 good chromium@454450 416.603 +- 21.5348 6 good chromium@454451 408.673 +- 45.3236 6 good chromium@454452 634.808 +- 14.296 6 bad <-- chromium@454454 633.744 +- 19.4046 6 bad chromium@454458 625.788 +- 52.8196 6 bad chromium@454465 638.609 +- 13.7205 6 bad chromium@454479 631.41 +- 24.55 6 bad chromium@454537 636.737 +- 33.2481 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 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8985754537512641696 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5868788043481088 | 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 liberato@google.com
, Mar 7 2017