From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XdG30-0006kB-UF for bitcoin-development@lists.sourceforge.net; Sun, 12 Oct 2014 10:06:42 +0000 X-ACL-Warn: Received: from calliope-smout.broadpark.no ([80.202.10.16]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1XdG2z-0007eS-E1 for bitcoin-development@lists.sourceforge.net; Sun, 12 Oct 2014 10:06:42 +0000 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from aqua-smin.broadpark.no ([80.202.10.60]) by caliope-smout.broadpark.no (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTP id <0NDB00B9UTEZ3820@caliope-smout.broadpark.no> for bitcoin-development@lists.sourceforge.net; Sun, 12 Oct 2014 12:06:35 +0200 (CEST) Received: from xr4.com ([80.202.94.109]) by aqua-smin.broadpark.no (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTP id <0NDB00F3QTEZR580@aqua-smin.broadpark.no> for bitcoin-development@lists.sourceforge.net; Sun, 12 Oct 2014 12:06:35 +0200 (CEST) Received: from [192.168.1.4] (grimreaper.xr4.com [192.168.1.4]) by xr4.com (Postfix) with ESMTP id 1617E20592; Sun, 12 Oct 2014 12:06:35 +0200 (CEST) Message-id: <543A52A1.2010408@bitminter.com> Date: Sun, 12 Oct 2014 12:06:25 +0200 From: Geir Harald Hansen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 To: Bitcoin Dev References: <543A3EB9.4040803@bitminter.com> In-reply-to: X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.202.10.16 listed in list.dnswl.org] X-Headers-End: 1XdG2z-0007eS-E1 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Oct 2014 10:06:43 -0000 On 12.10.2014 11:52, Wladimir wrote: > On Sun, Oct 12, 2014 at 10:41 AM, Geir Harald Hansen > 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. I was thinking of shorter sides of forks as being orphaned. Sorry for the confusion. Regards, Geir H. Hansen, Bitminter