Tags: Zondax/polkadot
Tags
pvf: Log memory metrics from preparation (paritytech#6565) * Add getrusage and memory tracker for precheck preparation * Log memory stats metrics after prechecking * Fix tests * Try to fix errors (linux-only so I'm relying on CI here) * Try to fix CI * Add module docs for `prepare/memory_stats.rs`; fix CI error * Report memory stats for all preparation jobs * Use `RUSAGE_SELF` instead of `RUSAGE_THREAD` Not sure why I did that -- was a brainfart on my end. * Revert last commit (RUSAGE_THREAD is correct) * Use exponential buckets * Use `RUSAGE_SELF` for `getrusage`; enable `max_rss` metric for MacOS * Increase poll interval * Revert "Use `RUSAGE_SELF` for `getrusage`; enable `max_rss` metric for MacOS" This reverts commit becf7a8.
added new bootnode to chain spec's (paritytech#2204) * added new bootnode to chain spec's * remove trailing newline
Backport substrate#7733 and switch to that branch (paritytech#2193)
[WIP] Update weights in prep for v0.8.27 (paritytech#2097) * Update weights for polkadot * add Kusama weights * add westend weights * remove claims weight files claims still uses in-line weights which is fine cause it is a polkadot specific pallet Co-authored-by: Parity Benchmarking Bot <admin@parity.io> Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
PreviousNext