blob: 53c77a8a9dc6c5a53bf5cf8b80e65cb4f51370b9 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
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 <mh.in.england@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <CANEZrP3WHA7P+t2Jk+w1kBMk0QuqN+gBXeNMoAnj_rK=nor-qg@mail.gmail.com>
References: <CANEZrP2xnsOHyH+a1g6qSNSx_g+TW-yvL0Due7PVr421U6kRLw@mail.gmail.com>
<CAAS2fgTNqUeYy+oEFyQWrfs4Xyb=3NXutvCmLusknF-18JmFQg@mail.gmail.com>
<CANEZrP2q9a_0rFh+oo6iUFF1goWs0OJO1xPvxC9zqNA-6VnFAQ@mail.gmail.com>
<CABsx9T3pQFqL0xsvRfnixYEATO61qMCCDdLmtqZkbVLW0Vxytg@mail.gmail.com>
<CANEZrP08NrCJM2gxNitXrLjuY6AusNULvkcheN_0MbgFQV_QXw@mail.gmail.com>
<4FE0D167.7030506@justmoon.de>
<CANEZrP3WHA7P+t2Jk+w1kBMk0QuqN+gBXeNMoAnj_rK=nor-qg@mail.gmail.com>
Date: Wed, 20 Jun 2012 11:53:32 +0200
X-Google-Sender-Auth: IA9ni1yjhCFMcAQxKIJPMkNvWGI
Message-ID: <CANEZrP2ztFOxVrUdewL-pM4Xy=kkU3WBUqdB9ixk05YGwFz6WQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Stefan Thomas <moon@justmoon.de>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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.
|
