Issue metadata
Sign in to add a comment
|
11.5%-23.4% regression in scheduler.tough_scheduling_cases at 483965:484027 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974916428263634144
,
Jul 5 2017
=== Auto-CCing suspected CL author skyostil@chromium.org === Hi skyostil@chromium.org, 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 : Sami Kyostila Commit : 56398249f62df4942576ebbaec482d6fd8cea9a7 Date : Mon Jul 03 15:26:15 2017 Subject: Remove synthetic delay framework Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : scheduler.tough_scheduling_cases Metric : queueing_durations/queueing_durations Change : 19.81% | 0.180680345613 -> 0.216467259911 Revision Result N chromium@483964 0.18068 +- 0.0026641 5 good chromium@483993 0.180065 +- 0.0106625 5 good chromium@484000 0.178629 +- 0.00384298 6 good chromium@484004 0.183578 +- 0.00769363 5 good chromium@484005 0.175309 +- 0.0113776 6 good chromium@484006 0.218518 +- 0.0175891 6 bad <-- chromium@484007 0.219147 +- 0.0146347 6 bad chromium@484021 0.216467 +- 0.0176498 6 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 scheduler.tough_scheduling_cases More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8974916428263634144 For feedback, file a bug with component Speed>Bisection
,
Jul 6 2017
Benchmarking change, not a real regression :) |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rmcilroy@chromium.org
, Jul 5 2017