MIME-Version: 1.0
Message-ID: <trinity-5fc3c701-4768-45bb-9a49-1214362e68be-1437676001187@3capp-mailcom-bs03>
From: "Slurms MacKenzie" <slurms@gmx.us>
To: "Eric Voskuil" <eric@voskuil.org>
Content-Type: text/plain; charset=UTF-8
Date: Thu, 23 Jul 2015 20:26:41 +0200
Importance: normal
Sensitivity: Normal
In-Reply-To: <55B1309D.7020209@voskuil.org>
References: <trinity-c358bbcc-a5d1-487f-9aae-730241fc4eac-1437666965282@3capp-mailcom-bs12>,
	<55B1309D.7020209@voskuil.org>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Electrum Server Speed Test
Precedence: list

That's purely the time on the wall for electrum-server, validation in bitcoind happens before. As ThomasV has pointed out it is significantly faster with a solid state disk (but much more expensive to operate), if we get to that point it'll only be expensive servers with lots of SSD space which are able to keep up with the current software. 

I was mostly trying to make a point about other software being impacted in ways which aren't really discussed, rather than a specific dig about electrum-server. I should have made that more clear. 


> Sent: Thursday, July 23, 2015 at 9:21 PM
> From: "Eric Voskuil" <eric@voskuil.org>
> To: "Slurms MacKenzie" <slurms@gmx.us>, bitcoin-dev@lists.linuxfoundation.org
> Subject: Re: [bitcoin-dev] Electrum Server Speed Test
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Does "to process into the index" include time for transport and/or
> block validation (presumably by bitcoind) or this this exclusively the
> time for Electrum Server to index a validated block?
> 
> e
>