From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Pull request: Optimize database writes for transactions with lots of TxIns.
Date: Mon, 5 Sep 2011 16:43:17 -0400 [thread overview]
Message-ID: <CABsx9T1g2p71YLeDz5mocUJTpjaKN0tKRaFQ_HcLWyKNOaT1pw@mail.gmail.com> (raw)
And I'd appreciate review/feedback on this:
https://github.com/bitcoin/bitcoin/pull/491
Patch from ArtForz, who discovered the problem.
The problem was chaining large transactions (transactions with lots of
ins and outs) would make the berkeley db transaction log get very big,
as the dependencies (TxIns) of a transaction might be re-written
multiple times.
With this fix, each each transaction referred to by TxIns is written once.
--
--
Gavin Andresen
reply other threads:[~2011-09-05 20:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CABsx9T1g2p71YLeDz5mocUJTpjaKN0tKRaFQ_HcLWyKNOaT1pw@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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