Weirdly, in my case syncing was faster on Windows than on Linux. Sometimes it seems like the process crashed because nothing is happening.Īs long as it didn't give an error that it crashed indeed, your Bitcoin Core client might simply be writing data to the disk, which doesn't impact the displayed data. I noted that if you close Bitcoin Core and launch it later to keep syncing, the speed will drastically reduce. Launch the initial sync and let it sync all the way through. It was indicating an average speed of 12% progress per hour, which makes it ~8hr.Īs I need the txindex, the data displayed on Bitcoin Core wasn't changing but the index files were created by the process : it didn't crash despite the info displayed remains still. In the end, it took ~20hr to fully sync from scratch. My RAM was filling up with raw block data, then Bitcoin Core processed it. I'm lucky : I have a 1Gb fiber connection. While looking at the resources manager, I noticed that the Bitcoin Core process took up to 12GB in RAM. I am only syncing up on that computer for now. There is an option in nf called dbcache.īy default, it limits the usage of RAM for Bitcoin Core and leave enough for the rest of your processes. I'm lucky to have 32Gb RAM on my Desktop computer. I ended up using an HDD that is directly wired to my motherboard with SATA, cutting out every interface. I hold this kind of data (blockchains) on drives I swap at need.ĭespite the rack receiver being wired to my motherboard with a SATA cable, when I used it as the data directory for Bitcoin Core, the speed for synchronization was insanely slow. I use a HDD rack to easily swap drives when needed. The input/output speed of the external device is a bottleneck and BTC will take ages to sync that way. I started zipping the blockchain directory on my server, to download it afterwards, but that also is very time extensive.īased on my trials, luckily there are a couple options / settings / things you can do to enhance the synchronization speed.ġ) Don't put your "bitcoin folder" on an external drive. I have another full node on a server, but can't access the HDD. I have good practices when it comes to handle crypto funds, so they were not at risk even in the case of total deletion of that bitcoin folder. When I tried to open it again, there was something wrong about the index, so I went on with provided instructions.Īt some point I realized that the folder with the data weights a mere 100's of MBs : all blockchain data was gone. ![]() BTW if you have time machine setup you may want to go into its preferences and exclude every file in the /Library/Application Support/Bitcoin/ except the wallet.dat this will save you gigabytes of easily replaced data being backed up every time it runs.Lately I have jammed my Bitcoin Core full node blockchain.ĭon't ask why, I am not sure what happened. Kind of hard to read but that pop up looks like it says you need another 6000 blocks to be caught up once it does download them you will see your btc. I am running Bitcoin-Qt v0.7.2-beta on OS X 10.7. In hindsight I was an idiot to send them while this was the case, but I don't think I can undo it now so I'd really appreciate it if someone more savvy could help me out of this mess. I'm sure this must have been the case since the moment I downloaded it, but just didn't realise until I'd sent the BTC. However I subsequently realised that my wallet in Bitcoin-Qt is constantly showing as "out of sync" despite the fact that I have been running the programme for hours, which means my BTC haven't arrived (20+ confirmations on ). I then sent them to the standard address given in the Bitcoin-Qt client I had downloaded. ![]() I'm a noob to Bitcoin and just bought my first BTC from bitbargain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |