Issue metadata
Sign in to add a comment
|
18% regression in thread_times.key_idle_power_cases at 514612:514710 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963323341398984240
,
Nov 11 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Ulan Degenbaev Commit : 6bb1d47e6e82f75ead36cdab209afc5dafa8329c Date : Tue Nov 07 13:11:10 2017 Subject: [heap] Re-enable concurrent marking. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : thread_times.key_idle_power_cases Metric : thread_total_all_cpu_time_per_second/animated-gif.html Change : 19.25% | 0.551708609221 -> 0.65790755151 Revision Result N chromium@514611 0.551709 +- 0.456407 14 good chromium@514636 0.585726 +- 0.278554 9 good chromium@514640 0.584265 +- 0.280054 9 good chromium@514641 0.586185 +- 0.278714 9 good chromium@514641,v8@67d543ec31 0.585688 +- 0.279367 9 good chromium@514641,v8@6bb1d47e6e 0.69011 +- 0.281221 9 bad <-- chromium@514641,v8@ac0661b358 0.690387 +- 0.283359 9 bad chromium@514641,v8@80cb266c75 0.698503 +- 0.285948 9 bad chromium@514642 0.694071 +- 0.287388 9 bad chromium@514643 0.694537 +- 0.283289 9 bad chromium@514649 0.691151 +- 0.285253 9 bad chromium@514661 0.688002 +- 0.279058 9 bad chromium@514710 0.657908 +- 0.451485 14 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=animated.gif.html thread_times.key_idle_power_cases More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963323341398984240 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 10 2017