From: "Slurms MacKenzie" <slurms@gmx.us>
To: lf-lists@mattcorallo.com
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Node Speed Test
Date: Fri, 24 Jul 2015 05:19:35 +0200 [thread overview]
Message-ID: <trinity-fedcdb1a-27cc-44cc-9638-be520331e59f-1437707974947@3capp-mailcom-bs10> (raw)
In-Reply-To: <55B1A763.3000000@mattcorallo.com>
Yes that is completely doable for the next crawl, however I am not sure how much that reflects the behavior bitcoind would see when making connections. Nodes do not make any attempt to sync with close peers, which is an undesirable property if you are attempting to be sybil resistant. With some quick playing around it seems that you do get the expected speedup with close proximity, but it's not a particularly huge difference at present. I'll keep working on it and see where I get.
> Sent: Friday, July 24, 2015 at 4:48 AM
> From: "Matt Corallo via bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org>
> To: bitcoin-dev@lists.linuxfoundation.org
> Subject: Re: [bitcoin-dev] Bitcoin Node Speed Test
>
> You may see much better throughput if you run a few servers around the
> globe and test based on closest-by-geoip. TCP throughput is rather
> significantly effected by latency, though I'm not really sure what you
> should be testing here, ideally.
next prev parent reply other threads:[~2015-07-24 3:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 14:19 [bitcoin-dev] Bitcoin Node Speed Test slurms
2015-07-23 15:04 ` Gavin Andresen
2015-07-23 15:55 ` Jameson Lopp
2015-07-23 17:14 ` Slurms MacKenzie
2015-07-23 17:41 ` Pindar Wong
2015-07-23 16:05 ` Peter Todd
2015-07-23 19:56 ` Marcel Jamin
2015-07-23 19:57 ` Joseph Gleason ⑈
2015-07-24 2:55 ` Peter Todd
2015-07-23 16:36 ` Leo Wandersleb
2015-07-23 17:12 ` Slurms MacKenzie
2015-07-24 2:48 ` Matt Corallo
2015-07-24 3:19 ` Slurms MacKenzie [this message]
2015-07-24 3:54 ` grarpamp
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-fedcdb1a-27cc-44cc-9638-be520331e59f-1437707974947@3capp-mailcom-bs10 \
--to=slurms@gmx.us \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=lf-lists@mattcorallo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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