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-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1USlEG-0006eV-Ds for bitcoin-development@lists.sourceforge.net; Thu, 18 Apr 2013 09:34:08 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.50 as permitted sender) client-ip=209.85.219.50; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f50.google.com; Received: from mail-oa0-f50.google.com ([209.85.219.50]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1USlEF-0003KO-MM for bitcoin-development@lists.sourceforge.net; Thu, 18 Apr 2013 09:34:08 +0000 Received: by mail-oa0-f50.google.com with SMTP id n1so2541443oag.37 for ; Thu, 18 Apr 2013 02:34:02 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.84.135 with SMTP id z7mr144744oby.35.1366277642259; Thu, 18 Apr 2013 02:34:02 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.167.169 with HTTP; Thu, 18 Apr 2013 02:34:02 -0700 (PDT) In-Reply-To: References: <453bfc69-b2ab-4992-9807-55270fbda0db@email.android.com> <20130418090444.GA30995@savin> Date: Thu, 18 Apr 2013 11:34:02 +0200 X-Google-Sender-Auth: eBie3Jy4E3EEQn4Ejf_SyRw_v1o Message-ID: From: Mike Hearn To: Peter Todd Content-Type: multipart/alternative; boundary=089e013a26968873a804da9f4dd1 X-Spam-Score: -0.5 (/) 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 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1USlEF-0003KO-MM Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Anti DoS for tx replacement 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: Thu, 18 Apr 2013 09:34:08 -0000 --089e013a26968873a804da9f4dd1 Content-Type: text/plain; charset=UTF-8 On Thu, Apr 18, 2013 at 11:28 AM, Mike Hearn wrote: > With the sipaspeed patches it seems ECDSA can be processed on modern cores > at something like 20,000 signatures per second. So it'd take a bit over 4 > seconds to process all of them (cpu time). > Sorry brainfart, s/cores/cpus/. I think the 20k/sec was with full usage of a hyperthreaded quad core CPU. --089e013a26968873a804da9f4dd1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Thu, Apr 18, 2013 at 11:28 AM, Mike Hearn <mike@plan99.n= et> wrote:
With the sipaspeed patches it seems ECDSA can be processed= on modern cores at something like 20,000 signatures per second. So it'= d take a bit over 4 seconds to process all of them (cpu time).

Sorry brainfart, s/cores/cpus/. I think the 20k/s= ec was with full usage of a hyperthreaded quad core CPU.
<= /div> --089e013a26968873a804da9f4dd1--