Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: darkfur93 on October 01, 2014, 09:10:00 AM



Title: Bitcoin-qt slow starting up, will increasing database cache help?
Post by: darkfur93 on October 01, 2014, 09:10:00 AM
I'm using v0.9.2.1-g354c0f3-beta linux 64-bit. May upgrade to 0.9.3 later on.
Right now it takes a few minutes to startup Bitcoin-qt after computer has been powered off. When Bitcoin-qt is running it's using 1.1GB of my 16GB of ram.

I have my database cache set to 100MB, will increasing it help speed it up?


Title: Re: Bitcoin-qt slow starting up, will increasing database cache help?
Post by: shorena on October 01, 2014, 11:05:33 AM
On startup its checking the last 288 blocks by default you can reduce the number of blocks with:
-checkblocks=<n>
and how thorough those blocks are checked with:
-checklevel=<n>
where n is an integer from 0 to 4 and 3 is the default setting.

You could also use:
-par=<n>
to set the number of cores to use, by default (n=0) its determined automatically.




Title: Re: Bitcoin-qt slow starting up, will increasing database cache help?
Post by: btckold24 on October 03, 2014, 07:23:36 AM
I had this problem also but just dealt with it - thx for the help shorena - looks like its working as I tried it on my other computers wallet


Title: Re: Bitcoin-qt slow starting up, will increasing database cache help?
Post by: zvs on October 03, 2014, 09:29:05 AM
Increasing database cache would make the initial load slower, afaik. 

I use checkblocks=10 in .conf on my home computer


Title: Re: Bitcoin-qt slow starting up, will increasing database cache help?
Post by: oser41eric on October 16, 2014, 01:13:54 PM
On startup its checking the last 288 blocks by default you can reduce the number of blocks with:
-checkblocks=<n>
and how thorough those blocks are checked with:
-checklevel=<n>
where n is an integer from 0 to 4 and 3 is the default setting.


At default settings it takes me about 20 minutes for the checking blocks stage. When I change to checklevel=1 the checking blocks stage takes only 2 seconds... So the question is how important is keeping the default setting. It seems I might not catch block database corruption at startup if I just use checklevel=1, so hard decision