From: "Slurms MacKenzie" <slurms@gmx•us>
To: "Eric Voskuil" <eric@voskuil•org>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Electrum Server Speed Test
Date: Thu, 23 Jul 2015 20:26:41 +0200 [thread overview]
Message-ID: <trinity-5fc3c701-4768-45bb-9a49-1214362e68be-1437676001187@3capp-mailcom-bs03> (raw)
In-Reply-To: <55B1309D.7020209@voskuil.org>
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
>
prev parent reply other threads:[~2015-07-23 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 15:56 Slurms MacKenzie
2015-07-23 17:18 ` Joseph Gleason ⑈
2015-07-23 17:28 ` Matt Whitlock
2015-07-23 17:41 ` Joseph Gleason ⑈
2015-07-23 17:58 ` Thomas Voegtlin
2015-07-23 18:21 ` Eric Voskuil
2015-07-23 18:26 ` Slurms MacKenzie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-5fc3c701-4768-45bb-9a49-1214362e68be-1437676001187@3capp-mailcom-bs03 \
--to=slurms@gmx$(echo .)us \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=eric@voskuil$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox