Issue metadata
Sign in to add a comment
|
56% regression in system_health.common_mobile at 496668:496950 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970286696088345616
,
Aug 25 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Brian White Commit : 7662ff8cb53121cd4d8916007d430b36efd45895 Date : Thu Aug 24 00:03:13 2017 Subject: Validate histograms before and after each task on Android. Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : system_health.common_mobile Metric : cpu_time_percentage_avg/browse_news/browse_news_washingtonpost Change : 53.94% | 0.731478563276 -> 1.12302148024 Revision Result N chromium@496667 0.731479 +- 0.0213185 9 good chromium@496809 0.749666 +- 0.0164018 7 good chromium@496845 0.743846 +- 0.00528683 6 good chromium@496863 0.746011 +- 0.016079 6 good chromium@496872 0.740452 +- 0.0155379 6 good chromium@496876 0.741409 +- 0.00992135 6 good chromium@496877 0.742528 +- 0.00825394 6 good chromium@496878 1.12489 +- 0.0154294 6 bad <-- chromium@496880 1.13213 +- 0.0153659 6 bad chromium@496950 1.12302 +- 0.0232657 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=browse.news.washingtonpost system_health.common_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8970286696088345616 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 25 2017