Issue metadata
Sign in to add a comment
|
4.9% regression in thread_times.simple_mobile_sites at 467926:467961 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980604966901833488
,
May 3 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: android_nexus7_perf_bisect Benchmark : thread_times.simple_mobile_sites Metric : thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame Change : 10.12% | 2.38480284484 -> 2.5714325312 Suspected Commit Range 4 commits in range https://chromium.googlesource.com/chromium/src/+log/a350792a1dfc14589c29942cb7349f4a5976d7d2..82ecc71c03b9c7a0478849b3df403c1518b05642 Revision Result N chromium@467925 2.3848 +- 0.249095 14 good chromium@467926 --- --- build failure chromium@467927 --- --- build failure chromium@467928 --- --- build failure chromium@467929 2.46073 +- 0.131722 14 bad chromium@467934 2.45099 +- 0.137064 14 bad chromium@467943 2.45363 +- 0.0840935 6 bad chromium@467961 2.57143 +- 0.128293 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.simple_mobile_sites Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980604966901833488 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5888235902861312 | 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!
,
Jul 7 2017
Too noisy, and have seen many other regressions/improvements since last bisect attempts. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by mustaq@chromium.org
, May 3 2017