From: Jeff Garzik <jgarzik@bitpay•com>
To: "Rune Kjær Svendsen" <runesvend@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Implementing batch processing for -blocknotify
Date: Fri, 31 May 2013 15:25:44 -0400 [thread overview]
Message-ID: <CAJHLa0M+EExHNMoQ7K3u8R6KHF-sZLbGcEoREyuZzwuvrn1zgQ@mail.gmail.com> (raw)
In-Reply-To: <CAH2=CKxBX6BcLS+CSKxZstut+uhHPQUY7HnLHSoMjZACgd4v1g@mail.gmail.com>
On Fri, May 31, 2013 at 8:37 AM, Rune Kjær Svendsen <runesvend@gmail•com> wrote:
> I've thought about this as well. It just seems somewhat clunky to me. I'd
> really prefer having bitcoind put out messages in batches, if it's doable,
> that is.
>
> I'd run into a lot of concurrency issues, as far as I can see, where I can't
> be sure that the queue isn't written to while, for example, it is opened by
> the program that needs to process the queue items.
>
> What if a disk operation takes a long time to finish, and a two queue
> operations want to add to the queue simultaneously? This really brings
> forward all the horrors of concurrent programming.
This is not a compelling need to update bitcoind for this.
The vast majority of systems are currently capable of processing a
block, before another block arrives.
As for parallel processing, your "what if" has been a solved problem
for decade(s) now.
--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2013-05-31 19:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 11:56 Rune Kjær Svendsen
2013-05-31 12:10 ` Michael Hendricks
2013-05-31 12:37 ` Rune Kjær Svendsen
2013-05-31 19:25 ` Jeff Garzik [this message]
2013-05-31 12:54 ` Andy Parkins
2013-05-31 13:05 ` Jeff Garzik
2013-05-31 22:20 ` Chris Double
2013-05-31 23:29 ` Wladimir
2013-05-31 23:47 ` Chris Double
2013-06-01 13:12 ` Rune Kjær Svendsen
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=CAJHLa0M+EExHNMoQ7K3u8R6KHF-sZLbGcEoREyuZzwuvrn1zgQ@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=runesvend@gmail$(echo .)com \
/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