From: Christian Decker <decker.christian@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>,
Michael Gronager <gronager@ceptacle•com>
Subject: Re: [Bitcoin-development] Network propagation speeds
Date: Wed, 27 Nov 2013 21:46:50 +0100 [thread overview]
Message-ID: <CALxbBHXBCNyWwkthaY=1VuS-H35zxnfEarPqhmJMvkmvCheciw@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP0SBSV_r6jieXSDB6FRFsFDcjxFH5hc4D3BpDgO7QxK6Q@mail.gmail.com>
Damn, that happens if I do the overview as an afterthought. Fixed :-)
Real time (last 24 hours, last week, last month) are in the pipeline,
just need to find the time to implement access to the collector from
the webpage.
--
Christian Decker
On Wed, Nov 27, 2013 at 8:35 PM, Mike Hearn <mike@plan99•net> wrote:
> Hey Christian,
>
> Could you sort the snapshots by date? At the moment they're kind of in a
> random order.
>
> Sometimes I wish we had real-time stats too but this is a great start.
>
>
> On Mon, Nov 25, 2013 at 8:27 PM, Christian Decker
> <decker.christian@gmail•com> wrote:
>>
>> Thanks Mike for the Tip :-)
>>
>> I will definitely extend the calculations to include a size-normalized
>> version. As for transaction propagations, being much smaller the
>> measurements tend to be much noisier, but given enough samples we
>> might be able to reconstruct some of the system parameters.
>>
>> Good idea to attempt to correlate propagation speed and number of
>> inputs/outputs, might be interesting to see whether processing at the
>> nodes has an influence.
>>
>> Regards,
>> Chris
>> --
>> Christian Decker
>>
>>
>> On Mon, Nov 25, 2013 at 9:51 AM, Michael Gronager <gronager@ceptacle•com>
>> wrote:
>> > Hi Christian,
>> >
>> > Cool - thanks for posting - agree, that it would be nice to normalize
>> > the results with block size - so divide by size and:
>> > 1. see if there is a correlation (we all presume there still is)
>> > 2. plot the delay graph as e.g. normalized to the averaged blocksize or
>> > lets define a "standard block size" of 200kb or what ever so we can
>> > compare the plot btw days.
>> >
>> > Also, does the correlation of propagation times hold for transaction
>> > sizes as well (would be ice to find the logical t0 and the constant - I
>> > guess the interesting measure is not kb but signatures, so number of
>> > inputs - some correlation with size though).
>> >
>> > Best,
>> >
>> > Michael
>> >
>> > On 24/11/13, 17:37 , Christian Decker wrote:
>> >> 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.
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> 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
>> >>
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > 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
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>
>
next prev parent reply other threads:[~2013-11-27 20:47 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 [this message]
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='CALxbBHXBCNyWwkthaY=1VuS-H35zxnfEarPqhmJMvkmvCheciw@mail.gmail.com' \
--to=decker.christian@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gronager@ceptacle$(echo .)com \
--cc=mike@plan99$(echo .)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