Comment
Author: Admin | 2025-04-28
Describe the issueMy bitcoin core wallet is taking a ridiculously long time to catch up to the blockchain. I've been running it on and off for a MONTH now, and I'm still 41 weeks behind. Looking at my Task Manager, I see that my network is being almost totally unutilized at 0.1Mbps, tho my disk is being used at 1.5 MBps. It also says the Bitcoin Core (GUI node for Bitcoin) is only using 280 MB of memory, even tho I have -dbcache=700 set in the config (which I can see it recognizes in the options since it lists it under "Active command-line options that override above options").I have also tried removing -dbcache=700 from my bitcoin.conf and instead setting 1000 MB as the database cache option in the GUI options window (and restarting of course). Neither the bitcoin.conf nor the database cache size option in the options seem to affect how much memory is allocated to bitcoin core, even tho I have at least 800MB free.What version of bitcoin-core are you using?Bitcoin Core version v0.14.1 (64-bit), officialMachine specs:OS: Windows 8.1 64-bitCPU: Intel Core i7-4702HQ @ 2.2 GHzRAM: 8 GBDisk size: 4TB HD for the blockchain, 250 GB SSD for the program and other (smaller) dataNetwork Speed: 50 MbpsAny extra information that might be useful in the debugging process.My debug.log (note the weird whitespace is verbatim): setting -whitelistrelay=12017-06-21 19:59:18 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.2017-06-21 19:59:18 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."2017-06-21 19:59:18 Default data directory C:\Users\fresheneesz\AppData\Roaming\Bitcoin2017-06-21 19:59:18 Using data directory H:\Bitcoin2017-06-21 19:59:18 Using config file H:\Bitcoin\bitcoin.conf2017-06-21 19:59:18 Using at most 125 automatic connections (2048 file descriptors available)2017-06-21 19:59:18 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements2017-06-21 19:59:18 Using 4 threads for script verification2017-06-21 19:59:18 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)2017-06-21 19:59:18 Using wallet wallet.dat2017-06-21 19:59:18 scheduler thread start2017-06-21 19:59:18 init message: Verifying wallet...2017-06-21 19:59:18 CDBEnv::Open: LogDir=H:\Bitcoin\database ErrorFile=H:\Bitcoin\db.log2017-06-21 19:59:18 Bound to [::]:83332017-06-21 19:59:18 Bound to 0.0.0.0:83332017-06-21 19:59:18 Cache configuration:2017-06-21 19:59:18 * Using 2.0MiB for block index database2017-06-21 19:59:18 * Using 8.0MiB for chain state database2017-06-21 19:59:18 * Using 990.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)2017-06-21 19:59:18 init message: Loading block index...2017-06-21 19:59:18 Opening LevelDB in H:\Bitcoin\blocks\index2017-06-21 19:59:18 Opened LevelDB successfully2017-06-21 19:59:18 Using obfuscation key for H:\Bitcoin\blocks\index: 00000000000000002017-06-21 19:59:18 Opening LevelDB in H:\Bitcoin\chainstate2017-06-21 19:59:19 Opened LevelDB successfully2017-06-21 19:59:19 Using obfuscation
Add Comment