Issue metadata
Sign in to add a comment
|
5.2%-9.1% regression in thread_times.tough_scrolling_cases at 524691:524859 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8959561853952233440
,
Dec 21 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : thread_times.tough_scrolling_cases Metric : thread_raster_cpu_time_per_frame/text_hover_10000_pixels_per_second Revision Result N chromium@524741 1.18984 +- 1.02717 21 good chromium@524859 1.19102 +- 1.02237 21 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.hover.10000.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/8959561853952233440 For feedback, file a bug with component Speed>Bisection
,
Jan 23 2018
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12fd03e4840000
,
Jan 23 2018
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14e3bed4840000
,
Jan 23 2018
Kicked off a few more bisects.
,
Jan 24 2018
๐ Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14e3bed4840000 Rework out-of-gamut handling in SkRasterPipeline By mtklein@chromium.org ยท Mon Dec 18 18:48:42 2017 +0000 skia @ 37155d476cd727329d985b75ecedbefe380a0f23 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jan 24 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 21 2017