From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Vl1p5-00065i-KV for bitcoin-development@lists.sourceforge.net; Mon, 25 Nov 2013 19:27:55 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.175 as permitted sender) client-ip=209.85.214.175; envelope-from=decker.christian@gmail.com; helo=mail-ob0-f175.google.com; Received: from mail-ob0-f175.google.com ([209.85.214.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Vl1p4-0006jR-Nw for bitcoin-development@lists.sourceforge.net; Mon, 25 Nov 2013 19:27:55 +0000 Received: by mail-ob0-f175.google.com with SMTP id uz6so4674683obc.20 for ; Mon, 25 Nov 2013 11:27:49 -0800 (PST) X-Received: by 10.60.136.196 with SMTP id qc4mr7154623oeb.41.1385407669325; Mon, 25 Nov 2013 11:27:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.130.198 with HTTP; Mon, 25 Nov 2013 11:27:09 -0800 (PST) In-Reply-To: <52930FA3.3070802@ceptacle.com> References: <52930FA3.3070802@ceptacle.com> From: Christian Decker Date: Mon, 25 Nov 2013 20:27:09 +0100 Message-ID: To: Michael Gronager Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: doubleclick.net] -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (decker.christian[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Vl1p4-0006jR-Nw Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Network propagation speeds X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 19:27:55 -0000 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 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 wrote: >>> On Sun, Nov 24, 2013 at 8:20 AM, Christian Decker >>> 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