Bitcoin Knots
30 posts
@1440000bytes @oomahq Looks like #32273 is the bugfix (fixing a bug that caused a mere error) that exposed Core to the worse (data loss causing) bug. This PR was _not_ merged into Knots yet. I am now fairly confident that @BitcoinKnots is NOT impacted by the Core30 wallet deletion bug.
More benchmarks! This time I synced Bitcoin Knots, for good measure! bitcoin.conf: dbcache=32000 assumevalid=0 stopatheight=850000 (Note that Knots respects the 32GB dbcache limit, the same as the Core master branch, but unlike Core v28). I added "stopatheight" because I wanted to include the shutdown time in the benchmark. For some reason there appears to be an off-by-one bug in this code, as the tip was at 850001 when Knots shut down. And on to the results: 13 hours, 18 minutes and 57 seconds. seconds: 47937 minutes: 799 hours: 13.32 This result is very close to the Core v28 result (47786 seconds), except I didn't include the shutdown time in that result, so this Knots benchmark is maybe ~20 minutes or so faster than Core v28! The shutdown took 1484 seconds (~25 minutes), so an apples-to-apples comparison between Knots and Core puts Knots at 12.9 hours, where core v28 took 13.27 hours and core master took 13.96 hours. So right now the rankings for a full validation run are: 1) Bitcoin Knots: 46453 seconds + 1484 shutdown time 2) Bitcoin Core v28: 47786 + ? shutdown time (16GB would take maybe 25 minutes?) 3) Bitcoin Core master branch: 50243 + 2563 shutdown time 4) libbitcoin dev build: 33510 for download and validation + ? (10 hours?) for confirmation stage, + ~10 seconds for shutdown So currently Knots has the fastest full-validation sync time of all the implementations on this hardware, congrats @BitcoinKnots! I do expect libbitcoin to jump up significantly once Eric is done optimizing the confirmation stage. Anyone want me to benchmark Knots with assumevalid on?
