public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andrew Chow <lists@achow101.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Huge wallets make Bitcoin Core unusable (Daemon+CLI & Qt)
Date: Sat, 20 Aug 2022 15:10:57 +0000	[thread overview]
Message-ID: <89f3e708-8096-e0eb-458c-0d0b4d844934@achow101.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 581 bytes --]

This is a known issue that I've been working on. The wallet is a large module in Bitcoin Core and changing it takes quite a bit of time.

On 08/20/2022 10:16 AM, Felipe Micaroni Lalli via bitcoin-dev wrote:

> 8.1) Can we "optimize" a huge wallet without moving the funds to a new one? Like a "fsck" or eqv?

You can remove old transactions using the removeprunedfunds RPC. That should greatly speed up balance calculations and transaction creation.

> 8.2) Can we improve the cache usage somehow? Putting the entire wallet in memory, for example?

It's already entirely in memory.

[-- Attachment #2: Type: text/html, Size: 1410 bytes --]

             reply	other threads:[~2022-08-20 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20 15:10 Andrew Chow [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-20 14:16 [bitcoin-dev] Huge wallets make Bitcoin Core unusable (Daemon+CLI & Qt) micaroni
2022-08-20 15:06 ` rhavar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=89f3e708-8096-e0eb-458c-0d0b4d844934@achow101.com \
    --to=lists@achow101.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox