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-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1ShHbY-0000JI-3b for bitcoin-development@lists.sourceforge.net; Wed, 20 Jun 2012 09:53:40 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.181 as permitted sender) client-ip=209.85.212.181; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f181.google.com; Received: from mail-wi0-f181.google.com ([209.85.212.181]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1ShHbX-0002rf-3L for bitcoin-development@lists.sourceforge.net; Wed, 20 Jun 2012 09:53:40 +0000 Received: by wibhn14 with SMTP id hn14so3265460wib.10 for ; Wed, 20 Jun 2012 02:53:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.99.70 with SMTP id eo6mr10616604wib.17.1340186012879; Wed, 20 Jun 2012 02:53:32 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.216.254.232 with HTTP; Wed, 20 Jun 2012 02:53:32 -0700 (PDT) In-Reply-To: References: <4FE0D167.7030506@justmoon.de> Date: Wed, 20 Jun 2012 11:53:32 +0200 X-Google-Sender-Auth: IA9ni1yjhCFMcAQxKIJPMkNvWGI Message-ID: From: Mike Hearn To: Stefan Thomas Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.4 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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 0.1 AWL AWL: From: address is in the auto white-list X-Headers-End: 1ShHbX-0002rf-3L Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] LevelDB benchmarking 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: Wed, 20 Jun 2012 09:53:40 -0000 There's an interesting post here about block propagation times: https://bitcointalk.org/index.php?topic=88302.msg975343#msg975343 Looks like the regular network is reliably 0-60 seconds behind p2pool in propagating new blocks. So optimizing IO load (and after that, threading tx verification) seems like an important win. Lukes preview functionality would also be useful.