Bitcoin Core 0.10.0 starts very slow.

[Amph]

How long does it usually take for the wallet to open if opened the first time of the day?

Depends on the hardware. On a fast desktop with a SSD, a 60+MB wallet full startup with default settings is under 20 seconds.

Hardware is quite decent. I can only dream of having Bitcoin Core start under 60 seconds.

Is it also possible that switching wallet files could cause the wallet to open very slow?

But then again, it still should start within a few minutes.

Just stopped the time. The system is 5-6 years old and the bottle neck is the HDD. The CPU still has capacity left and launching bitcoin core/qt took a little less than 53,128 seconds.

Its set to check the last 24 blocks at default checklevel.

I think the problem is as good as solved. I can only hope it will stay like this.

Today the wallet managed to open in less than 60 secons. 47 seconds to be precise.

i'm at 25 secs, tried it now

i7 4790k(4400) + 16 giga of ram

so the problem must be a slow machine for the OP

[zvs]

If it's not because of the block checking, it's probably because you have some massive wallet.  Maybe a lot of satoshi dicing in your past, I dunno.

this:

Code:

2015-03-27 08:10:02 Verifying last 5 blocks at level 3
2015-03-27 08:10:05 No coin database inconsistencies in last 6 blocks (1653 transactions)
2015-03-27 08:10:05  block index           15513ms
2015-03-27 08:10:05 No wallet compiled in!
2015-03-27 08:10:05 mapBlockIndex.size() = 349505
2015-03-27 08:10:05 nBestHeight = 349428
2015-03-27 08:10:05 init message: Loading addresses...
2015-03-27 08:10:05 Loaded 14862 addresses from peers.dat  146ms

is how long it takes to load on a VIA Nano U2250 with some rubbish 160GB HDD and 2GB RAM.    (but I don't use wallet on these nodes of course)

[unamis76]

Bitcoin Core always took something like 20 minutes to boot around here (the disadvantages of not having an SSD...). Never really worried about it, but it would be cool if I could speed it up a bit. Doesn't lowering the number of blocks checked at startup make my wallet a disservice to the community? Could I be relaying imprecise blockchain data if I do that? Would my connections be rejected if I had a somewhat wrong blockchain?

[Borisz]

Bitcoin Core always took something like 20 minutes to boot around here (the disadvantages of not having an SSD...). Never really worried about it, but it would be cool if I could speed it up a bit. Doesn't lowering the number of blocks checked at startup make my wallet a disservice to the community? Could I be relaying imprecise blockchain data if I do that? Would my connections be rejected if I had a somewhat wrong blockchain?

I wouldn't say you disservice the community. You are still running a fully node, but before startup you only check, say the last 10 blocks. The chances of those all being generated by an attack and hence being fake, are small (I'd think so anyway).

Worst that could happen in my opinion:
You receive X fake blocks generated and then you shut down your client. After some time you restart the client, but your last X blocks are wrong, hence the check will return an error. I am not sure what would happen, maybe you would need to recheck the blockchain or re-download. However I think this is unlikely.

When I set up my client to check only the last few blocks (10-20) the client started in a fraction of the time than what it used to be. Regardless, I have just recently switched to Multibit as 30+ GB of HDD space is something I simply cannot afford just to store some mBTC.

[unamis76]

Bitcoin Core always took something like 20 minutes to boot around here (the disadvantages of not having an SSD...). Never really worried about it, but it would be cool if I could speed it up a bit. Doesn't lowering the number of blocks checked at startup make my wallet a disservice to the community? Could I be relaying imprecise blockchain data if I do that? Would my connections be rejected if I had a somewhat wrong blockchain?

I wouldn't say you disservice the community. You are still running a fully node, but before startup you only check, say the last 10 blocks. The chances of those all being generated by an attack and hence being fake, are small (I'd think so anyway).

Worst that could happen in my opinion:
You receive X fake blocks generated and then you shut down your client. After some time you restart the client, but your last X blocks are wrong, hence the check will return an error. I am not sure what would happen, maybe you would need to recheck the blockchain or re-download. However I think this is unlikely.

When I set up my client to check only the last few blocks (10-20) the client started in a fraction of the time than what it used to be. Regardless, I have just recently switched to Multibit as 30+ GB of HDD space is something I simply cannot afford just to store some mBTC.

That was precisely my fear, having to reindex the whole blockchain... I think I'll change the block checking anyways, thank you

[BrianM]

Bitcoin Core always took something like 20 minutes to boot around here (the disadvantages of not having an SSD...). Never really worried about it, but it would be cool if I could speed it up a bit. Doesn't lowering the number of blocks checked at startup make my wallet a disservice to the community? Could I be relaying imprecise blockchain data if I do that? Would my connections be rejected if I had a somewhat wrong blockchain?

I have a crappy old 7200 RPM, which I found in the dumpster.
It works pretty ok for the core. But yes, SSD would speed things up.
But overall 3 min start up with a wood-computer with a old magnetic drive is not too bad.

[memai]

I also encountered the same situation as you . My Bitcoin clients start very slow.  My connecting network is good. What I should do atm ?

Thanks !

[unamis76]

Bitcoin Core always took something like 20 minutes to boot around here (the disadvantages of not having an SSD...). Never really worried about it, but it would be cool if I could speed it up a bit. Doesn't lowering the number of blocks checked at startup make my wallet a disservice to the community? Could I be relaying imprecise blockchain data if I do that? Would my connections be rejected if I had a somewhat wrong blockchain?

I have a crappy old 7200 RPM, which I found in the dumpster.
It works pretty ok for the core. But yes, SSD would speed things up.
But overall 3 min start up with a wood-computer with a old magnetic drive is not too bad.

What did you change in your configuration to get 3 minutes start time? I have my blockchain files on a WD Caviar Blue 1TB. It's not a old disk but still takes much more time than your disk.

[Borisz]

I also encountered the same situation as you . My Bitcoin clients start very slow.  My connecting network is good. What I should do atm ?

Thanks !

If you are using qt then you can add

Code:

checkblocks=10

to your conf file. Your client will only recheck the last 10 blocks and start considerably faster.

[toytoboy]

As the title states.

I have been browsing through the forum to find a solution but so far failed in doing so.

It takes nearly 15-20 minutes to open, it keeps saying checking blocks, but how many times will it check them??

The previous version took around 15 minutes to open, and current version takes even longer while it was quite fast when I installed it after the update release.

Full blockchain is on my windows 7 computer, and my computer has decent specs, nothing to worry about.

Are there any nodes that I need to add in order to get it working faster? Not sure what the problem is.

I have also such the same statement ! Please help !Thanks !

[Borisz]

As the title states.

I have been browsing through the forum to find a solution but so far failed in doing so.

It takes nearly 15-20 minutes to open, it keeps saying checking blocks, but how many times will it check them??

The previous version took around 15 minutes to open, and current version takes even longer while it was quite fast when I installed it after the update release.

Full blockchain is on my windows 7 computer, and my computer has decent specs, nothing to worry about.

Are there any nodes that I need to add in order to get it working faster? Not sure what the problem is.

I have also such the same statement ! Please help !Thanks !

Have you tried what was suggested in the first reply? Or what I wrote just before your comment?

[Odalv]

I moved data data to external HD.

When I start bitcoin-QT I see message "Activating best chain..." for few hours.  Processor is on 3%.

Can somebody help me ?

[Odalv]

I moved data data to external HD.

When I start bitcoin-QT I see message "Activating best chain..." for few hours.  Processor is on 3%.

Can somebody help me ?

When I turn Avast(antivirus) off then qt starts working fine.

[shorena]

I moved data data to external HD.

When I start bitcoin-QT I see message "Activating best chain..." for few hours.  Processor is on 3%.

Can somebody help me ?

When I turn Avast(antivirus) off then qt starts working fine.

They might - still - detect the virus signatures someone put in the blockchain a few years (?) ago.

[Adrian-x]

I moved data data to external HD.

When I start bitcoin-QT I see message "Activating best chain..." for few hours.  Processor is on 3%.

Can somebody help me ?

try running Bitcoin XT

[ethought]

I moved data data to external HD.

When I start bitcoin-QT I see message "Activating best chain..." for few hours.  Processor is on 3%.

Can somebody help me ?

I did the same thing, moved datadir to an external HDD, now "Activating best chain..." has been showing for at least 10 hours. No updates in debug.log during this time, so not even sure if anything is happening at all.

[HarHarHar9965]

Bitcoin Core once again is very slow and takes over 10 minutes just to open. I think my 1tb hdd is the bottleneck here.

While it is checking blocks I can't use the pc for browsing and such as it completely takes over my hdd.

It's a Seagate Barracuda 7200 RPM with 64MB cache. I think this drive is decent enough to be capable of running the wallet.

Bitcoin Core now uses header first synchronization. This means that we first ask peers for block headers then we have to validate that for an initial full synchronization. You may notice a slower progress in the very first few minutes, when headers are still being fetched and verified