📅 Original date posted:2015-07-23
📝 Original message:-----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
On 07/23/2015 08:56 AM, Slurms MacKenzie via bitcoin-dev wrote:
> Similar to the Bitcoin Node Speed Test, this is a quick
> quantitative
look at how the Electrum server software handles under load. The
Electrum wallet is extremely popular, and the distributed servers
which power it are all hosted by volunteers without budget. The server
requires a fully indexed Bitcoin Core daemon running, and produces
sizable external index in order to allow SPV clients to quickly
retrieve their history.
>
>
> 3.9G electrum/utxo 67M electrum/undo 19G electrum/hist
> 1.4G electrum/addr 24G electrum/
>
>
> Based on my own logs produced by the electrum-server console, it
takes this server (Xeon, lots of memory, 7200 RPM RAID) approximately
3.7 minutes per megabyte of block to process into the index. This
seems to hold true through the 10 or so blocks I have in my scroll
buffer, the contents of blocks seem to be of approximately the same
processing load. Continuing this trend with the current inter-block
time of 9.8 minutes, an electrum-server instance running on
modest-high end dedicated server is able to support up to 2.64 MB
block sizes before permanently falling behind the chain.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVsTCdAAoJEDzYwH8LXOFOLpgIAIAe5QBTTgpe2kyYrqamUKNI
uasljmNQi3In/rdxNm9Ga+vwTsBg7f4v/xHVrQYAGxdjjZxs0h9bOmAvuc+p2fad
ZeHC/vewrtLxB2aVj5JVbSk5ik57ePyk3SmghTpGMAhgTIWkceIrxR+Fq7TFOlqn
NGnTuBSSsGL9nY57hIFwMJb2CKdPwMVLL/0gjVQ9Llqt+Fu31eSRhDzHOvJnkofO
xwVrVGgST2GE73np3WA0jvzRHjFgsPnQknhjLGQiTgDKsKL0BywE9/Vke2zVNyP7
cAlTQoScEal++9u0h3D475lsxv43V0Rxafc7W0a/OyfXujJ2AlixgV8PlLwhvaY=
=DK5K
-----END PGP SIGNATURE-----
Eric Voskuil [ARCHIVE] /
npub1sg…ppx3c
2023-06-07 15:43:29
in reply to nevent1q…ul86
Author Public Key
npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3cPublished at
2023-06-07 15:43:29Event JSON
{
"id": "08c859d552f5ec6c171a8c77c7a2ab72e39ca4414976f327a77d4956007bc950",
"pubkey": "82205f272f995d9be742779a3c19a2ae08522ca14824c3a3b01525fb5459161e",
"created_at": 1686152609,
"kind": 1,
"tags": [
[
"e",
"3bf103a91ccfc68d15572c2de8b2ed4dbf981bdf21125d9bbe75c38503c33e24",
"",
"root"
],
[
"e",
"e2dddeccf48dee585d7cc7541a4fd4c944b349ca8fb1fd6e596485bb38945045",
"",
"reply"
],
[
"p",
"7a4ba40070e54012212867182c66beef592603fe7c7284b72ffaafce9da20c05"
]
],
"content": "📅 Original date posted:2015-07-23\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\nDoes \"to process into the index\" include time for transport and/or\nblock validation (presumably by bitcoind) or this this exclusively the\ntime for Electrum Server to index a validated block?\n\ne\n\nOn 07/23/2015 08:56 AM, Slurms MacKenzie via bitcoin-dev wrote:\n\n\u003e Similar to the Bitcoin Node Speed Test, this is a quick\n\u003e quantitative\nlook at how the Electrum server software handles under load. The\nElectrum wallet is extremely popular, and the distributed servers\nwhich power it are all hosted by volunteers without budget. The server\nrequires a fully indexed Bitcoin Core daemon running, and produces\nsizable external index in order to allow SPV clients to quickly\nretrieve their history.\n\u003e \n\u003e \n\u003e 3.9G electrum/utxo 67M electrum/undo 19G electrum/hist \n\u003e 1.4G electrum/addr 24G electrum/\n\u003e \n\u003e \n\u003e Based on my own logs produced by the electrum-server console, it\ntakes this server (Xeon, lots of memory, 7200 RPM RAID) approximately\n3.7 minutes per megabyte of block to process into the index. This\nseems to hold true through the 10 or so blocks I have in my scroll\nbuffer, the contents of blocks seem to be of approximately the same\nprocessing load. Continuing this trend with the current inter-block\ntime of 9.8 minutes, an electrum-server instance running on\nmodest-high end dedicated server is able to support up to 2.64 MB\nblock sizes before permanently falling behind the chain.\n\n\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1\n\niQEcBAEBAgAGBQJVsTCdAAoJEDzYwH8LXOFOLpgIAIAe5QBTTgpe2kyYrqamUKNI\nuasljmNQi3In/rdxNm9Ga+vwTsBg7f4v/xHVrQYAGxdjjZxs0h9bOmAvuc+p2fad\nZeHC/vewrtLxB2aVj5JVbSk5ik57ePyk3SmghTpGMAhgTIWkceIrxR+Fq7TFOlqn\nNGnTuBSSsGL9nY57hIFwMJb2CKdPwMVLL/0gjVQ9Llqt+Fu31eSRhDzHOvJnkofO\nxwVrVGgST2GE73np3WA0jvzRHjFgsPnQknhjLGQiTgDKsKL0BywE9/Vke2zVNyP7\ncAlTQoScEal++9u0h3D475lsxv43V0Rxafc7W0a/OyfXujJ2AlixgV8PlLwhvaY=\n=DK5K\n-----END PGP SIGNATURE-----",
"sig": "78232de13ec8afa0c9151273441e3a36b649dd55f3e59a97949c5d247f931e390246bc82577ff37c65d9c53330c43a8ac19de469d9c186f0d6673b2f02a2ba64"
}