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-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1WXDai-0007Fv-3N
	for bitcoin-development@lists.sourceforge.net;
	Mon, 07 Apr 2014 17:44:16 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.177 as permitted sender)
	client-ip=209.85.217.177; envelope-from=gmaxwell@gmail.com;
	helo=mail-lb0-f177.google.com; 
Received: from mail-lb0-f177.google.com ([209.85.217.177])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WXDah-0004VW-Dg
	for bitcoin-development@lists.sourceforge.net;
	Mon, 07 Apr 2014 17:44:16 +0000
Received: by mail-lb0-f177.google.com with SMTP id z11so5055468lbi.36
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 07 Apr 2014 10:44:08 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.234.130 with SMTP id ue2mr22206289lac.0.1396892648736;
	Mon, 07 Apr 2014 10:44:08 -0700 (PDT)
Received: by 10.112.89.68 with HTTP; Mon, 7 Apr 2014 10:44:08 -0700 (PDT)
In-Reply-To: <CANEZrP3_v2zAqMkcTtQ1Mys2rUEcsd_MpLySefpgJ-P7OSg34g@mail.gmail.com>
References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com>
	<5342C833.5030906@gmail.com>
	<CAAS2fgTqBfEPXh2dfcL_ke6c0wfXw4qUM1rAYMkAHcAM6mYH+g@mail.gmail.com>
	<5342D1DB.8060203@monetize.io>
	<CAAS2fgRu-0C_ozaN0qSc9SvF2TpZ56NwceLCrfQjikuQgc85tQ@mail.gmail.com>
	<5342D9FA.8080102@monetize.io>
	<CAAS2fgT5xfYzup01+USkFmFWi=FtDfbPY1HPpTLyQ+6_ejGOZA@mail.gmail.com>
	<CACvcBVq2+37jWgxBg2Zjj6KFtT1ZnZzTa7FOw1sLwimeT0ahhA@mail.gmail.com>
	<CANEZrP3_v2zAqMkcTtQ1Mys2rUEcsd_MpLySefpgJ-P7OSg34g@mail.gmail.com>
Date: Mon, 7 Apr 2014 10:44:08 -0700
Message-ID: <CAAS2fgSbqSbX7WX5S=UMWz-4vfnEQCKMTTC8cWTT7KJvOZX54A@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: 1.1 (+)
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
	(gmaxwell[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
	[Blocked - see <http://www.spamcop.net/bl.shtml?209.85.217.177>]
	-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
	1.5 SF_NO_SPF_SPAM         SF_NO_SPF_SPAM
X-Headers-End: 1WXDah-0004VW-Dg
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
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: Mon, 07 Apr 2014 17:44:16 -0000

On Mon, Apr 7, 2014 at 10:40 AM, Mike Hearn <mike@plan99.net> wrote:
> Actually, I wonder

The actual validation isn't really the problem today. The slowness of
the IBD is almost exclusively the lack of parallel fetching and the
existence of slow peers.  And making the signature gate adaptive (and
deploying the 6x faster ECDSA code) would improve that future.

Go grab sipa's headers first branch, it has no problem saturating a
20mbit/sec pipe syncing up.