Issue metadata
Sign in to add a comment
|
176.4% regression in media.tough_video_cases at 467620:467677 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980775461467901392
,
May 1 2017
,
May 1 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : media.tough_video_cases Metric : energy_consumption_mwh/video.html?src_tulip2.m4a_type_audio Change : 14.60% | 17.6263464065 -> 20.199025472 Suspected Commit Range 3 commits in range https://chromium.googlesource.com/chromium/src/+log/dfd5b6f49e5382da44646018e2471a3e9f15f96f..15e8fb8c185a6137e42c895401c127972249d26f Revision Result N chromium@467619 17.6263 +- 0.927523 14 good chromium@467634 17.5938 +- 0.72451 9 good chromium@467638 18.0709 +- 3.94834 14 good chromium@467639 --- --- build failure chromium@467640 --- --- build failure chromium@467641 20.249 +- 13.4309 14 bad chromium@467648 17.9264 +- 0.818031 14 bad chromium@467677 20.199 +- 13.7381 14 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=video.html.src.tulip2.m4a.type.audio media.tough_video_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980775461467901392 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5868605436067840 | 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 11 2017
as per c#4, perf regression is on src_tulip2.m4a_type_audio. give to dale to start investigation.
,
May 15 2017
Seems to have fixed itself. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by w...@chromium.org
, May 1 2017