Issue metadata
Sign in to add a comment
|
6.2%-621.8% regression in smoothness.gpu_rasterization.top_25_smooth at 511313:511540 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8964269742107752480
,
Oct 31 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_nexus5X_perf_bisect Benchmark : thread_times.tough_scrolling_cases Metric : thread_raster_cpu_time_per_frame/text_constant_full_page_raster_60000_pixels_per_second Change : 4.93% | 4.2660650348 -> 4.06681517706 Suspected Commit Range 3 commits in range https://chromium.googlesource.com/chromium/src/+log/cd32fdf5709b0ec9aa71502dfec1e84f8f3567c3..a198fc24fe25a6f04bbe2264b28571f580bfe579 Revision Result N chromium@511424 4.26607 +- 0.434166 14 good chromium@511428 4.21751 +- 0.404596 14 good chromium@511429 --- --- build failure chromium@511430 --- --- build failure chromium@511431 4.12691 +- 0.439805 14 bad chromium@511432 4.11186 +- 0.344352 14 bad chromium@511439 4.13811 +- 0.299343 14 bad chromium@511453 4.13895 +- 0.397708 14 bad chromium@511482 4.07246 +- 0.254046 9 bad chromium@511540 4.06682 +- 0.228927 9 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 --story-filter=text.constant.full.page.raster.60000.pixels.per.second thread_times.tough_scrolling_cases More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8964269742107752480 For feedback, file a bug with component Speed>Bisection
,
Oct 31 2017
@yukishiino: Of the 3 patches in the range https://chromium.googlesource.com/chromium/src/+/a198fc24fe25a6f04bbe2264b28571f580bfe579 looks the most suspect. Can you take a look?
,
Oct 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8964188835348897008
,
Oct 31 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : David Bokan Commit : dbab215523c8d77a7b54fcf3776357b079c36899 Date : Tue Oct 24 14:24:10 2017 Subject: Fix telemetry gesture speeds Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : thread_times.tough_scrolling_cases Metric : thread_total_all_cpu_time_per_frame/text_constant_full_page_raster_15000_pixels_per_second Change : 9.31% | 25.947428276 -> 28.3643747072 Revision Result N chromium@511393 25.9474 +- 0.287926 6 good chromium@511396 25.8272 +- 0.903972 6 good chromium@511397 26.2463 +- 1.20066 6 good chromium@511397,catapult@f9691b256a 26.7621 +- 1.88498 6 good chromium@511397,catapult@dbab215523 28.5284 +- 0.545044 6 bad <-- chromium@511397,catapult@2f4cf37a9f 28.2683 +- 0.770058 6 bad chromium@511398 28.149 +- 0.311488 6 bad chromium@511402 28.1501 +- 1.15455 6 bad chromium@511410 28.4712 +- 0.642025 6 bad chromium@511426 28.3644 +- 0.304836 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 --story-filter=text.constant.full.page.raster.15000.pixels.per.second thread_times.tough_scrolling_cases More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8964188835348897008 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 30 2017