From: Mike Hearn <mike@plan99•net>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Network propagation speeds
Date: Sun, 24 Nov 2013 17:38:57 +0100 [thread overview]
Message-ID: <CANEZrP3=L-jutLZjg4DDqR-78RnxXRgtSuCr8hTbHZUogNBMSA@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQxBVOT1ceWWttH5e2wG7-qJ3LxKKnFBEqLwbz-OwDo3g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]
This is great, thanks for doing it. Tip sent your way.
Graphs of how propagation data change over time would also be helpful (as
well as raw data so we can calculate overhead per kilobyte and so on). I
know there are only two days worth of data, but for future, it'd be good.
I think the next part of figuring out why there's such huge disparity is
instrumenting bitcoind to find out where the time goes when relaying a
block.
On Sun, Nov 24, 2013 at 5:26 PM, Gregory Maxwell <gmaxwell@gmail•com> wrote:
> On Sun, Nov 24, 2013 at 8:20 AM, Christian Decker
> <decker.christian@gmail•com> wrote:
> > Since this came up again during the discussion of the Cornell paper I
> > thought I'd dig up my measurement code from the Information
> > Propagation paper and automate it as much as possible.
>
> Could you publish the block ids and timestamp sets for each block?
>
> It would be useful in correlating propagation information against
> block characteristics.
>
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up
> now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 2431 bytes --]
next prev parent reply other threads:[~2013-11-24 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 16:20 Christian Decker
2013-11-24 16:26 ` Gregory Maxwell
2013-11-24 16:37 ` Christian Decker
2013-11-25 8:51 ` Michael Gronager
2013-11-25 19:27 ` Christian Decker
2013-11-27 19:35 ` Mike Hearn
2013-11-27 20:46 ` Christian Decker
2013-11-24 16:38 ` Mike Hearn [this message]
2013-11-24 17:13 ` Peter Todd
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='CANEZrP3=L-jutLZjg4DDqR-78RnxXRgtSuCr8hTbHZUogNBMSA@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@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