You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The easy solution is https://dev.kilt.io/docs/chain/collator/#benchmarking We can outline how a collator runner can benchmark their machine. Basically let them build a binary with the runtime-benchmarks flag and optimizations, run the benchmark and compare to our official weights. If their weights are lower or insignificantly higher, then the machine should be fine
or we can provide a benchmarking binary as one of the release artifacts
The easy solution is https://dev.kilt.io/docs/chain/collator/#benchmarking We can outline how a collator runner can benchmark their machine. Basically let them build a binary with the runtime-benchmarks flag and optimizations, run the benchmark and compare to our official weights. If their weights are lower or insignificantly higher, then the machine should be fine
or we can provide a benchmarking binary as one of the release artifacts
The other solution is to implement a subcommand similar to polkadot's https://github.com/paritytech/polkadot/blob/master/cli/src/command.rs#L442
This checks pvf generation time, which is not exactly the what we want for collators. but we could implement something similar. The baseline benchmark looks okay.
The text was updated successfully, but these errors were encountered: