Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.219.47 as permitted sender)
	client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com;
	helo=mail-oa0-f47.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <533427EA.5010300@gmx.de>
References: <CANEZrP2hbBVGqytmXR1rAcVama4ONnR586Se-Ch=dsxOzy2O4w@mail.gmail.com>
	<lgvobr$q44$1@ger.gmane.org> <53340426.4040208@gmx.de>
	<CANEZrP1v7ZCmhhoHmuXXXvKwAV1_0a02Vkf9z4nQGNfAbZBM=A@mail.gmail.com>
	<533427EA.5010300@gmx.de>
Date: Thu, 27 Mar 2014 14:38:36 +0100
Message-ID: <CANEZrP2stoAD7s9o=rjAH30PaMb3vuf5py_TGhcOftSHnR=Oyg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Thomas Voegtlin <thomasv1@gmx.de>
Content-Type: multipart/alternative; boundary=047d7b5d524ebe458704f596b378
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New BIP32 structure
Precedence: list

--047d7b5d524ebe458704f596b378
Content-Type: text/plain; charset=UTF-8

>
> To be honest, I have not carried out a comprehensive examination of
> server performance. What I can see is that Electrum servers are often
> slowed down when a wallet with a large number (thousands) of addresses
> shows up, and this is caused by disk seeks (especially on my slow VPS).
>

Yes that sounds more like what I expected.


> In terms of bandwidth, I am referring to my Android version of Electrum.
> When it runs on a 3G connection, it sometimes takes up to 1 minute to
> synchronize (with a wallet that has hundreds of addresses). However, I
> have not checked if this was caused by addresses or block headers.
>

An address is 160 bits. (1000 * 160) / 8 / 1024 = 19.5 kilobytes of data
which 3G should be able to transfer in <1 second easily. Of course the
encoding may not be optimal. But if it is, I suspect the issue is elsewhere.

--047d7b5d524ebe458704f596b378
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">
<div class=3D"">To be honest, I have not carried out a comprehensive examin=
ation of<br></div>
server performance. What I can see is that Electrum servers are often<br>
slowed down when a wallet with a large number (thousands) of addresses<br>
shows up, and this is caused by disk seeks (especially on my slow VPS).<br>=
</blockquote><div><br></div><div>Yes that sounds more like what I expected.=
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);bo=
rder-left-style:solid;padding-left:1ex">
In terms of bandwidth, I am referring to my Android version of Electrum.<br=
>
When it runs on a 3G connection, it sometimes takes up to 1 minute to<br>
synchronize (with a wallet that has hundreds of addresses). However, I<br>
have not checked if this was caused by addresses or block headers.<br></blo=
ckquote><div><br></div><div>An address is 160 bits.=C2=A0(1000 * 160) / 8 /=
 1024 =3D 19.5 kilobytes of data which 3G should be able to transfer in &lt=
;1 second easily. Of course the encoding may not be optimal. But if it is, =
I suspect the issue is elsewhere.</div>
</div></div></div>

--047d7b5d524ebe458704f596b378--