diff options
author | Wladimir J. van der Laan <laanwj@gmail.com> | 2017-07-17 17:16:00 +0200 |
---|---|---|
committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2017-07-17 17:16:12 +0200 |
commit | 0b019357ff09e7a522307fc271d6b60562a7b890 (patch) | |
tree | 553c4968c81ba459fdc909520c5649b0da9ff877 /src/txdb.h | |
parent | 89bb0365b97af7a6f46b010ceb9ff31627a8f9db (diff) | |
parent | b0e8e2de8408cbaed9d70914c67b4c9f11397cb7 (diff) | |
download | bitcoin-0b019357ff09e7a522307fc271d6b60562a7b890.tar.xz |
Merge #10831: Batch flushing operations to the walletdb during top up and increase keypool size.
b0e8e2d Print one log message per keypool top-up, not one per key. (Gregory Maxwell)
41dc163 Increase wallet default keypool size to 1000. (Gregory Maxwell)
30d8f3a Pushdown walletdb though CWallet::AddKeyPubKey to avoid flushes. (Gregory Maxwell)
3a53f19 Pushdown walletdb object through GenerateNewKey/DeriveNewChildKey. (Gregory Maxwell)
Pull request description:
This carries the walletdb object from top-up through GenerateNewKey/DeriveNewChildKey/CWallet::AddKeyPubKey, which allows us to avoid the flush on destruction until the top up finishes instead of flushing the wallet for every key.
This speeds up adding keys by well over 10x on my laptop (actually something like 17x), I wouldn't be surprised if it were an even bigger speedup on spinning rust.
Then it increases the keypool size to 1000. I would have preferred to use 10,000 but in the case where the user creates a new wallet and then turns on encryption it seems kind of dumb to have >400KB of marked-used born unencrypted keys just laying around.
(Thanks to Matt for cluesticking me on how to bypass the crypter spaghetti)
Tree-SHA512: 868303de38fce4c3f67d7fe133f765f15435c94b39d252d7450b5fee5c607a3cc2f5e531861a69d8c8877bf130e0ff4c539f97500a6bc0ff6d67e4a42c9385c7
Diffstat (limited to 'src/txdb.h')
0 files changed, 0 insertions, 0 deletions