=== Auto-CCing suspected CL author herb@google.com ===
Hi herb@google.com, the bisect results pointed to your CL, please take a look at the
results.
=== BISECT JOB RESULTS ===
Perf regression found with culprit
Suspected Commit
Author : Herb Derby
Commit : 8a0d2d4af840fbd861d6e4444346c90c67dede13
Date : Wed Aug 16 03:59:53 2017
Subject: Start using linear filter for small sigma
Bisect Details
Configuration: win_perf_bisect
Benchmark : rasterize_and_record_micro.top_25
Metric : rasterize_time/Facebook
Change : 21.23% | 2.693 -> 3.26483333333
Revision Result N
chromium@494643 2.693 +- 0.0995992 6 good
chromium@494670 2.67 +- 0.0753658 6 good
chromium@494684 2.69167 +- 0.0536594 6 good
chromium@494688 2.70817 +- 0.0630463 6 good
chromium@494690 2.66317 +- 0.0496269 6 good
chromium@494691 3.21683 +- 0.0369707 6 bad <--
chromium@494697 3.20983 +- 0.0432069 6 bad
chromium@494750 3.26483 +- 0.0795414 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 --story-filter=Facebook rasterize_and_record_micro.top_25
More information on addressing performance regressions:
http://g.co/ChromePerformanceRegressions
Debug information about this bisect:
https://chromeperf.appspot.com/buildbucket_job_status/8970272163048642928
For feedback, file a bug with component Speed>Bisection
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 25 2017