[ ] Commit the current 'official' benchmarks resulting from running remote benchmarks on the master branch. Include as JSON in the filecoin/json here.
[ ] Match and reconcile naming, and add automated import to merge these values into the defaults, so we are not using any hard-coded performance numbers in our calculations.
[ ] Iterate on naming until the Filecoin schema and key names emitted from rust-fil-proofs benchmarks agree. This may require filing issues in rust-fil-proofs or communicating directly with @laser .
[ ] Arrange for a single output file from rust-fil-proofs (see details below).
[ ] Potentially automate regular integration of latest benchmarks.
Then, click on the latest green build. Then, click on metrics_capture job. Then, click on either Run hash-constraints benchmarks on remote host, Run micro benchmarks, or Run ZigZag benchmarks using 1GiB sectors.
If these files are imported manually and given the sensible names included in the following command, it will assemble them into an acceptable 'canonical' single json import file.
NOTE: this script assumes but does not check that the three component JSON files are consistent and contain identical objects for the values of the git and system keys in their respective top-level objects. This is a valid assumption when all three JSON files have been harvested from the same CircleCI metrics_capture job.
For the initial version, commit that script (or some variant) and run it as part of the import process. Formalizing this process will simplify new manual imports for now. Later this step can be moved to rust-fil-proofs so we only receive the assembled result.
filecoin/json
here.rust-fil-proofs
benchmarks agree. This may require filing issues inrust-fil-proofs
or communicating directly with @laser .rust-fil-proofs
(see details below).To get the latest benchmarks, click here: https://circleci.com/gh/filecoin-project/workflows/rust-fil-proofs/tree/master
Then, click on the latest green build. Then, click on
metrics_capture
job. Then, click on eitherRun hash-constraints benchmarks on remote host
,Run micro benchmarks
, orRun ZigZag benchmarks using 1GiB sectors
.If these files are imported manually and given the sensible names included in the following command, it will assemble them into an acceptable 'canonical' single json import file.
NOTE: this script assumes but does not check that the three component JSON files are consistent and contain identical objects for the values of the
git
andsystem
keys in their respective top-level objects. This is a valid assumption when all three JSON files have been harvested from the same CircleCImetrics_capture
job.For the initial version, commit that script (or some variant) and run it as part of the import process. Formalizing this process will simplify new manual imports for now. Later this step can be moved to
rust-fil-proofs
so we only receive the assembled result.