From: Wladimir <laanwj@gmail•com>
To: Chris Double <chris.double@double•co.nz>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Implementing batch processing for -blocknotify
Date: Sat, 1 Jun 2013 01:29:46 +0200 [thread overview]
Message-ID: <CA+s+GJBo18mC84=09vEYZ0n7WVeA0MV2OfdvFDap0_sW7TinyA@mail.gmail.com> (raw)
In-Reply-To: <CALn1vHG5VbT4BeFW89DCAx0fzkjaGpABEMEZO42pAs-wdi-e5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
Chris,
Using zmq is a great fit for high-speed notifications such as this. Have
you seen the pull request to integrate zmq directly into bitcoind, so that
you don't even need -blocknotify?
https://github.com/bitcoin/bitcoin/pull/2415
If not: we could use some testing there!
Wladimir
On Sat, Jun 1, 2013 at 12:20 AM, Chris Double <chris.double@double•co.nz>wrote:
> On Fri, May 31, 2013 at 11:56 PM, Rune Kjær Svendsen
> <runesvend@gmail•com> wrote:
> > I'm not quite so how to go about this.
>
> As others have said, queuing outside of bitcoind is a better approach.
> I use zeromq for this situation. blocknotify runs a program which uses
> zeromq's pub/sub to queue and the application subscribes to this to
> get notified of the data.
>
> --
> http://www.bluishcoder.co.nz
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 2337 bytes --]
next prev parent reply other threads:[~2013-05-31 23:29 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
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 [this message]
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='CA+s+GJBo18mC84=09vEYZ0n7WVeA0MV2OfdvFDap0_sW7TinyA@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=chris.double@double$(echo .)co.nz \
/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