validation: write chainstate to disk every ~hour~ 10 minutes #109
Conversation
l0rinc
changed the title
l0rinc
force-pushed
the
detached108
branch
2 times, most recently
from
3833948 to
e2a994d
Compare
|
Timed out after 10 hours, let's try fewer blocks for mainnet-large (disabled the others ones as they're not important in this usecase) |
|
Changed the flushing interval to ~10 minutes to see how it behaves on a shorter timescale |
|
📊 Benchmark results for this run (12723550148) will be available at: https://bitcoin-dev-tools.github.io/benchcoin/results/pr-109/12723550148/index.html after the github pages "build and deployment" action has completed. |
l0rinc
changed the title
|
📊 Benchmark results for this run (12724747149) will be available at: https://bitcoin-dev-tools.github.io/benchcoin/results/pr-109/12724747149/index.html after the github pages "build and deployment" action has completed. |
Remove the 24 hour periodic flush interval and write the chainstate along with blocks and block index every hour
Co-Authored-By: l0rinc <[email protected]>
Co-Authored-By: Pieter Wuille <[email protected]> Co-Authored-By: l0rinc <[email protected]>
disabled signet & mainnet-default as only mainnet-large is important
Co-authored-by: Pieter Wuille <[email protected]> Co-authored-by: Martin Leitner-Ankerl <[email protected]>
|
Now that the plots are fixed and memory is measured, let's see the effect of this change |
|
📊 Benchmark results for this run (12829689522) will be available at: https://bitcoin-dev-tools.github.io/benchcoin/results/pr-109/12829689522/index.html after the github pages "build and deployment" action has completed. |
4 participants
Want to see the plots of bitcoin#30611 - expanding the target blocks to max (will take some time)