public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Christian Decker <decker.christian@gmail.com>
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:37:25 +0100	[thread overview]
Message-ID: <CALxbBHX9PACKFJM_-=0Hm7hO7Km7jnLNRk=pRcKYTAcPD4G5qg@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQxBVOT1ceWWttH5e2wG7-qJ3LxKKnFBEqLwbz-OwDo3g@mail.gmail.com>

Sure thing, I'm looking for a good way to publish these measurements,
but I haven't found a good option yet. They are rather large in size,
so I'd rather not serve them along with the website as it hasn't got
the capacity. Any suggestions? If the demand is not huge I could
provide them on a per user basis.
--
Christian Decker


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.



  reply	other threads:[~2013-11-24 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24 16:20 [Bitcoin-development] Network propagation speeds Christian Decker
2013-11-24 16:26 ` Gregory Maxwell
2013-11-24 16:37   ` Christian Decker [this message]
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
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='CALxbBHX9PACKFJM_-=0Hm7hO7Km7jnLNRk=pRcKYTAcPD4G5qg@mail.gmail.com' \
    --to=decker.christian@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gmaxwell@gmail.com \
    /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