Issue metadata
Sign in to add a comment
|
A zero-to-nonzero regression in blink_perf.owp_storage at 513500:513928 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 6 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963663310698133888
,
Nov 6 2017
=== Auto-CCing suspected CL author mek@chromium.org === Hi mek@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 : Marijn Kruisselbrink Commit : 9a0e42a43b3a5bdcb81d8fb4617537156631d032 Date : Fri Nov 03 18:18:50 2017 Subject: Add Registry::RegisterBlob trace event to mojo codepath. Bisect Details Configuration: win_x64_perf_bisect Benchmark : blink_perf.owp_storage Metric : Registry::RegisterBlob/Registry::RegisterBlob Revision Result N chromium@513776 0.0 +- 0.0 6 good chromium@513825 0.0 +- 0.0 6 good chromium@513838 0.0 +- 0.0 6 good chromium@513839 0.0 +- 0.0 6 good chromium@513840 18.2224 +- 0.645376 6 bad <-- chromium@513841 18.3961 +- 0.166849 6 bad chromium@513844 18.4079 +- 0.249828 6 bad chromium@513850 18.4609 +- 0.508425 6 bad chromium@513874 8.49168 +- 0.253011 6 bad Please refer to the following doc on diagnosing blink_perf regressions: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.owp_storage More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963663310698133888 For feedback, file a bug with component Speed>Bisection
,
Nov 6 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 6 2017