Bitcoin Forum
June 14, 2024, 09:22:10 AM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin-qt 25% CPU and 500MB RAM  (Read 1074 times)
lontivero (OP)
Full Member
***
Offline Offline

Activity: 164
Merit: 128

Amazing times are coming


View Profile
November 28, 2014, 11:15:05 PM
 #1

Hi,

I wanted to consolidate all my wallets in one, just to have only one balance (because I has some satoshis here and there) so, I did a wallet backup 328 KBs and restore a 2 year-old wallet that I had with several small transactions and also imported the wallets that I had in my other computers. Finally I imported the backuped wallet's private keys. After that (almost 40 minutes), I had a 8MBs wallet and the bitcoin-qt client started to use 25% CPU and almost 500MBs RAM.

After this I restored the 328KBs wallet (it has just a couple of addresses and transactions) and all go back to normal. Is this the expected consumption?  
Meuh6879
Legendary
*
Offline Offline

Activity: 1512
Merit: 1011



View Profile
November 28, 2014, 11:59:16 PM
 #2

if you open the debug.log ... you can see that bitcoin core must read all the block since the creation of your wallet.
not a problem.

when i have restored my january 2014 wallet, i must wait like 2 minutes.

all android wallet does the same think (with merkle tree summary).

---

decrease cache to 4Mb in bitcoin core help a lot in poor system (2go of RAM) ... but request more reading on disc in node mode.
lontivero (OP)
Full Member
***
Offline Offline

Activity: 164
Merit: 128

Amazing times are coming


View Profile
November 29, 2014, 12:07:13 AM
 #3

if you open the debug.log ... you can see that bitcoin core must read all the block since the creation of your wallet.
not a problem.

when i have restored my january 2014 wallet, i must wait like 2 minutes.

all android wallet does the same think (with merkle tree summary).

---

decrease cache to 4Mb in bitcoin core help a lot in poor system (2go of RAM) ... but request more reading on disc in node mode.

I know that. The problem is that it was consuming that cpu and memory forever, even after calculate the final balance.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!