send BTC is very slow...

[livte]

  my wallet.dat size : 358M
and debug.log

    2016-02-06 17:03:09 keypool added key 54799, size=301
    2016-02-06 17:03:09 keypool reserve 54499
    2016-02-06 17:03:19 CommitTransaction:
    CTransaction(hash=3dc010c216, ver=1, vin.size=1, vout.size=2, nLockTime=397048)
        CTxIn(COutPoint(5fc29785f4, 41), scriptSig={{hash}}, nSequence=4294967294)
        CTxOut(nValue=3.37993552, scriptPubKey=OP_DUP OP_HASH160 {{hash}})
        CTxOut(nValue=0.68241470, scriptPubKey=OP_DUP OP_HASH160 {{hash}})
    2016-02-06 17:03:19 keypool keep 54499
    2016-02-06 17:03:19 AddToWallet {{hash}}  new
    2016-02-06 17:03:19 AddToWallet {{hash}}
    2016-02-06 17:03:19 Relaying wtx {{hash}}
    2016-02-06 17:03:37 keypool added key 54800, size=301
    2016-02-06 17:03:37 keypool reserve 54500
    2016-02-06 17:03:47 CommitTransaction:
        CTransaction(hash={{hash}}, ver=1, vin.size=1, vout.size=2, nLockTime=397048)
        CTxIn(COutPoint({{hash}}, 1), scriptSig={{hash}}, nSequence=4294967294)
        CTxOut(nValue=6.11253197, scriptPubKey=OP_DUP OP_HASH160 {{hash}})
        CTxOut(nValue=0.61373803, scriptPubKey=OP_DUP OP_HASH160 {{hash}})

I need more fast to send BTC(now 1 send be ~30sec) , but...I don't know how to fix it

the CUP usage always 100%+ , and my bitcoin.conf

    upnp=0
    maxconnections = 128
    server=1
    rpcthreads=8
    rpckeepalive=false
    rpctimeout=30
    rpcallowip=127.0.0.1
    rpcport=8332
    keypool=300
    paytxfee=0.0001

and getinfo

    {
    "version" : 110200,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 1800.54035850,
    "blocks" : 397059,
    "timeoffset" : -14,
    "connections" : 14,
    "proxy" : "",
    "difficulty" : 120033340651.23696899,
    "testnet" : false,
    "keypoololdest" : 1454771625,
    "keypoolsize" : 301,
    "paytxfee" : 0.00010000,
    "relayfee" : 0.00005000,
    "errors" : ""
    }

please help me to fix it....many thanx...

[1714932313]

1714932313

[1714932313]

1714932313

[1714932313]

1714932313

[1714932313]

1714932313

[cr1776]

Looks like your wallet.dat size is huge (size and number of keys). Why do you have it so large?  That is almost definitely the problem.

To verify, if you move your old wallet.dat (and have a backup) and relaunch it, is it more responsive?

How much ram etc is on your machine? CPU? OS?

[unamis76]

That's just the way it is... Your file is huge. Time for a new one (or a bigger machine... although the software might not be able to handle such a large file even with big resources.)

An example on wallet.dat size impact... I don't know how you are patient to sync it (or maybe you have it on 24/7)

Lets see:

	|	~size	|	#TX
fresh	|	96KB	|	0
regular	|	2MB	|	~300
spam[1]	|	421MB	|	195508

[1] its the ~100 leaked private keys related to the spam attack. I opened and resynced it just for this thread which took me ~7 hours. Bitcoin core acts very slow with such a big wallet file. It was ~110 MB before opening it, most of the time was resyncing.

[shorena]

That's just the way it is... Your file is huge. Time for a new one (or a bigger machine... although the software might not be able to handle such a large file even with big resources.)

An example on wallet.dat size impact... I don't know how you are patient to sync it (or maybe you have it on 24/7)

Lets see:

	|	~size	|	#TX
fresh	|	96KB	|	0
regular	|	2MB	|	~300
spam[1]	|	421MB	|	195508

[1] its the ~100 leaked private keys related to the spam attack. I opened and resynced it just for this thread which took me ~7 hours. Bitcoin core acts very slow with such a big wallet file. It was ~110 MB before opening it, most of the time was resyncing.

Nice digging, I actually cant open the spam file anymore. Not sure why, but core just hangs itself. From the log OP posted it looks like they cranked up their keypool for some reason.

Code:

  2016-02-06 17:03:37 keypool reserve 54500

What does the debug.log say directly after you start the wallet?

There should be something like this:

Code:

2016-02-05 05:50:07 init message: Loading wallet...
2016-02-05 05:50:07 nFileVersion = 110200
2016-02-05 05:50:07 Keys: 0 plaintext, xxx encrypted, xxx w/ metadata, xxx total

Alternativly, what does getwalletinfo return for keypoolsize?