substrate VS arewefastyet

Substrate — a framework for building application-specific blockchains (written in Rust);

frame-benchmarking = { version = "4.0.0-dev", default-features = false, optional = true, git = "https://github.com/paritytech/substrate.git", branch = "polkadot-v1.0.0" }

To offer some perspective outside of the typical "all crypto is a scam", Parity is doing some cool stuff with a rust modular blockchain library called Substrate https://github.com/paritytech/substrate.

Rust takes the cake in the blockchain space: Substrate, Cosmos (CosmWasm), and Solana. All of the zero knowledge cryptography libraries used for layer 2 solutions are written in Rust, compiling to Wasm (see arkworks, Risc0). Ethereum's next version of smart contracts will even use a restricted subset of Wasm ("Ewasm") instead of EVM.

Verifying NPoS election solution graph and its score is a memory-intensive operation that needs to be performed within a single block time. Under the current runtime constraints, a solution graph with 22,500 nominators can be verified well within the block production time on Polkadot. There are plans to improve on this and implement multi-block election solution verification, after which, the NPoS system can scale to incorporate more nominators.

Fast-unstake is now available on Kusama. This allows instant unstaking if you have not participated in staking in the last 28 eras. https://github.com/paritytech/substrate/pull/12129

First, any outstanding multisig calls (ones where one signatory has signed, but not the threshold) will not be able to execute. Please either finish your multisig calls before this upgrade, or wait until after it is completed. https://github.com/paritytech/substrate/pull/12072

Github: https://github.com/paritytech/substrate

That page averages all the builds across different code bases. It doesn’t specify which version/tag of which code base, nor does it talk about the hardware.

https://arewefastyet.pages.dev/ - This page tracks compile times across some common crates over all supported compiler versions, with different hardware (2, 4, 8, 16 cores). This used to be https://arewefastyet.rs but the domain expired.

https://arewefastyet.rs/ see benchmark

You can check incremental compile times on http://arewefastyet.rs. Choose one compile mode (Debug OR Release, preferably Debug), one hardware config (4 cores let's say) and both profile modes (Clean, Incremental).

Compile times in rustc have been steadily improving with time, as shown here - https://arewefastyet.rs.

Every release doesn't make every workload faster, but over a long time horizon, the effect is clear. Rust 1.34 was released in April 2019 and since then many crates have become 33-50% faster to compile, depending on the hardware and the compiler mode (clean/incremental, check/debug/release).

Interestingly, the speedup mentioned in OP won't show up in these charts because that's a change on macOS and these benchmarks were recorded on Linux.

What is expected to be a gamechanger is the release of cranelift in 2021 or 2022. It's an alternate debug backend that promises much faster debug builds.

Yes plenty of effort goes into making Rust compilation faster, see https://arewefastyet.rs/, its FAQ, and some easy internet searches.

Thanks for your work on arewefastyet.rs, I was about to post a link to it haha

I implemented something similar. Deserialising a comma separated strings into a struct - example. Hope that helps!