Issue metadata
Sign in to add a comment
|
83% regression in service_worker.service_worker_micro_benchmark at 453399:453481 |
||||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 7 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985805061394976272
,
Mar 7 2017
,
Mar 7 2017
=== Auto-CCing suspected CL author csharrison@chromium.org === Hi csharrison@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 : csharrison Commit : a17c6984f4b9369e8ce061018d31e4ecf64f7fdf Date : Tue Feb 28 02:18:11 2017 Subject: Do not schedule to load pending startable request on RemoveRequest Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : service_worker.service_worker_micro_benchmark Metric : concurrent_10_response_50_percentile/concurrent_10_response_50_percentile Change : 69.18% | 29.8166666667 -> 50.4425 Revision Result N chromium@453398 29.8167 +- 1.85152 6 good chromium@453440 29.2742 +- 1.55289 6 good chromium@453451 29.8592 +- 1.11104 6 good chromium@453456 30.2183 +- 2.66612 6 good chromium@453458 30.3108 +- 2.3583 6 good chromium@453459 51.6658 +- 9.90114 6 bad <-- chromium@453461 50.8533 +- 10.0097 6 bad chromium@453481 50.4425 +- 10.935 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 service_worker.service_worker_micro_benchmark Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8985805061394976272 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5289742029029376 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Mar 7 2017
I think we can merge this to the original bug. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by falken@chromium.org
, Mar 7 2017