From: Mike Hearn <mike@plan99•net>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Adding a pong message to the protocol
Date: Mon, 5 Sep 2011 16:32:36 +0200 [thread overview]
Message-ID: <CANEZrP3NU4tp2JD7syF6bvOn0JEv5M8rsadpMpuBJ-KLs8ETvw@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQdRP5bd02tR_L6_hWh+qEwXWOVH8KRcpuFiRvKwD5o1w@mail.gmail.com>
> I'd rather see effort spent on the root issues, e.g. having nodes
> gauge their own suitability (working inbound port, reasonably current
> block chain, etc) before becoming advertised listeners.
They can't always judge it, eg if the link between you and that peer
is saturated then you may have connectivity, but it may be very slow
yet appear fast to the node itself.
This really has two parts:
(1) Making it easy to determine latency
(2) Using that data to make better connection decisions
Adding a pong message is fairly trivial and can help solve (1). For
instance we can start building latency histograms of nodes to see how
performant the network is, without risking any issues. Then that data
can be used to inform simulations of what happens if the measurements
are used by the node software. It also lets us experiment with less
critical software like Android clients.
prev parent reply other threads:[~2011-09-05 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 12:04 Mike Hearn
2011-09-05 13:30 ` Gregory Maxwell
2011-09-05 14:32 ` Mike Hearn [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=CANEZrP3NU4tp2JD7syF6bvOn0JEv5M8rsadpMpuBJ-KLs8ETvw@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(echo .)com \
/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