Issue metadata
Sign in to add a comment
|
Aligning toolchain nightly perf tests with crosbolt |
||||||||||||||||||||||
Issue descriptionCurrently the benchmark sets being tracked are different. There can be regressions in crosbolt that we won't catch in our dashboard. In other words, the toolchain upgrade can be surprising to crosbolt. Tasks can be splitted into 1. update crosperf to run the required benchmarks. 2. update crostc_perf to include the required measurements. 3. update the dashboards to select the required measurements.
,
Feb 10 2018
,
Feb 10 2018
Hi Rahul, crostc_perf.proto doesn't contain some of the measurements that crosbolt looks at. For example, the database doesn't have the following: page_cycler_v2.typical_25/timeToFirstContentfulPaint_avg However, we did upload the original result.json, which contains the required information. Is it possible to update history in the database so that the dashboards can query the newly added measurements?
,
Feb 12 2018
Yes, it is easy to re-process the json files that have the new data once crostc_perf.proto is updated. All you need to do is move those json files back to the "~/pending_archives" directory and the next run of "archive_test_results.py" will reprocess them and update the columnio files. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by laszio@chromium.org
, Feb 10 2018