clarinet integrate and Devnets in general takes 3 to 5m to spin up. Looking at all the things being done under the hood, it's acceptable but we could deliver a better / faster experience which would result in more productivity.
Assuming developers are not customizing the devnet miner private keys (both bitcoin and stacks), when producing the bitcoin and stacks nodes docker images, we could warmup these 2 chains locally:
Bitcoin chain: produce the 109 blocks on the bitcoin chain
Stacks chain: sync the headers and blocks of these 109 blocks (including a leader key registration anchored in block 109).
We could then include an archive of these 2 states in the containers before publishing these images, and have the Devnet orchestrator use these chainstates when a Devnet is being spawed.
This approach could shave 2 to 3m from the boot sequence.
lgalabru
commented
2 years ago
clarinet integrateand Devnets in general takes 3 to 5m to spin up. Looking at all the things being done under the hood, it's acceptable but we could deliver a better / faster experience which would result in more productivity. Assuming developers are not customizing the devnet miner private keys (both bitcoin and stacks), when producing the bitcoin and stacks nodes docker images, we could warmup these 2 chains locally:We could then include an archive of these 2 states in the containers before publishing these images, and have the Devnet orchestrator use these chainstates when a Devnet is being spawed. This approach could shave 2 to 3m from the boot sequence.