-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catching up with the blockchain is slow #20
Comments
I've created several new issues which are targeted at optimizations areas revealed by profiling which can be used to track progress on this front. They are all tagged optimization. There have already been a few optimization related commits in the past couple of days since this issue was created that are working toward speeding things up. |
The signature verifications are now 10x faster as of commit btcsuite/btcec@ac7e4de. This results in a significant impact on the download speed after the final checkpoint (roughly 10x faster). |
Closing this as all of the optimizations noted above in conjunction with headers-first mode have been implemented and are included in the btcd 0.5.0-alpha release. Please note that the database is still slower than it should be and this is being tracked by #24. Note that even with the slower database, several of us have done head-to-head tests of downloading the full block chain as compared to bitcoind and btcd is slightly faster in most scenarios. The only time it has been measurably slower is on machines with slow disk I/O. As noted above this is the result of the slower database. |
This commit also fixes a couple of comment typos found while adding support for ListReceivedByAddress. Closes btcsuite#20.
ffldb: Support storing spend journals and switch to mutable treap
I have been syncing on and off for over 48 hours and have not caught up with the entire blockchain yet. Both CPU usage (<5%) and Disk usage (1MB/s) appear to be low.
I am running an instance of BitcoinQT on the same box and used --addpeer to try to kick it in the butt. Right now, I appear to be averaging less than a block every 5 seconds. Issue #12 mentions that various speed optimizations are planned.
The text was updated successfully, but these errors were encountered: