Issue metadata
Sign in to add a comment
|
19% regression in smoothness.tough_animation_cases at 495788:495808 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 24 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970368661542338176
,
Aug 24 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Nico Weber Commit : 7cd2f6bd73c6a9c6200704e995b18ebb3168ead6 Date : Sat Aug 19 04:23:54 2017 Subject: win: Turn off clang-by-default again for now. Bisect Details Configuration: win_8_perf_bisect Benchmark : smoothness.tough_animation_cases Metric : frame_times/overlay_background_color_css_transitions.html Change : 25.45% | 132.423873772 -> 166.126845945 Revision Result N chromium@495787 132.424 +- 5.1602 6 good chromium@495798 130.613 +- 3.31941 6 good chromium@495801 129.004 +- 7.15924 6 good chromium@495802 168.909 +- 3.9969 6 bad <-- chromium@495803 169.43 +- 12.2619 6 bad chromium@495808 166.127 +- 6.86481 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=overlay.background.color.css.transitions.html smoothness.tough_animation_cases More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8970368661542338176 For feedback, file a bug with component Speed>Bisection
,
Sep 21 2017
Issue 758594 has been merged into this issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 24 2017