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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1XdFpO-0004Sf-1R
for bitcoin-development@lists.sourceforge.net;
Sun, 12 Oct 2014 09:52:38 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.170 as permitted sender)
client-ip=209.85.213.170; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f170.google.com;
Received: from mail-ig0-f170.google.com ([209.85.213.170])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XdFpN-0004Q4-7o
for bitcoin-development@lists.sourceforge.net;
Sun, 12 Oct 2014 09:52:38 +0000
Received: by mail-ig0-f170.google.com with SMTP id hn15so11081144igb.5
for <bitcoin-development@lists.sourceforge.net>;
Sun, 12 Oct 2014 02:52:31 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.43.66.19 with SMTP id xo19mr29152232icb.31.1413107551897;
Sun, 12 Oct 2014 02:52:31 -0700 (PDT)
Received: by 10.64.141.112 with HTTP; Sun, 12 Oct 2014 02:52:31 -0700 (PDT)
In-Reply-To: <543A3EB9.4040803@bitminter.com>
References: <CAPg+sBjG86ZYKZZXA4VCMiFhz0sdxr_so41Zr+DATOXyRa9_Jw@mail.gmail.com>
<543A3EB9.4040803@bitminter.com>
Date: Sun, 12 Oct 2014 11:52:31 +0200
Message-ID: <CA+s+GJA=zgacbURh83DKyAV=x_t15xT=5cJTwSY8Omk2XZyuxA@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Geir Harald Hansen <operator@bitminter.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
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
(laanwj[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: 1XdFpN-0004Q4-7o
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Request for review/testing: headers-first
synchronization in Bitcoin Core
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: Sun, 12 Oct 2014 09:52:38 -0000
On Sun, Oct 12, 2014 at 10:41 AM, Geir Harald Hansen
<operator@bitminter.com> wrote:
> On 12.10.2014 01:34, Pieter Wuille wrote:
>> * No orphan blocks stored in memory anymore (reducing memory usage during sync).
>
> Will this slow down reorgs after a fork, compared to today?
Why would you think so? Orphan blocks are blocks whose parent is not
known. In the case of a reorganization the client 'jumps' to a new
best chain, for this to happen the original tip and the new best tip
and all their parents must be already known.
Wladimir
|
