Subject: Re: [Bitcoin-development] statoshi.info is now live

From: Josh Lehan <[email-masked]>
Date: Tue, 13 May 2014 10:48:19 -0700

I agree, it looks very slick.  Well done.

While on the subject of connected peers, what about the idea of adding the ping time from this node to other peers?  The problem with fitting that information into the current design is that the graphs seem to be comprised of overall statistics for this node, not per-peer statistics that can vary between peers (such as ping time).  If a line were to be added to a graph to represent each peer's ping time, the number of lines (statistics) on the graph would have to vary in real time as peers are added or removed, which would be a challenge.

I earlier added the "ping" feature to bitcoind, and it works to measure the ping time, however this feature is on-demand: it won't ping other nodes unless requested.  So, something would have to send the "ping" RPC command on a regular schedule, to ensure the graph is updated with new information.  Also, there is currently no support for overlapping pings (although that would be easy to add), so if a peer is slow enough to not respond at all to the first ping request, and a second ping request goes out in the meantime, any late response from the first ping request would then be discarded.

Great graphs, and these are just brainstorms for future ideas :)

Josh Lehan

Sent from my iPad

> On May 13, 2014, at 4:43, Wladimir <[email-masked]> wrote:
> 
> Hello Jameson,
> 
>> On Sun, May 11, 2014 at 7:14 PM, Jameson Lopp <[email-masked]> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> Since it seems unlikely that we'll be able to ship an integrated stats / monitoring feature in the short term, I went ahead and set up a public Statoshi instance and threw a nicer interface on top of it.
>> 
>> http://statoshi.info
> 
> Must say it looks very nice.
> 
> One comment about the graphs: in the 'connected peers' chart you
> visualize some larger quantities (especially knownAddresses) and some
> very small ones (peer.(dis)connect). This makes the latter invisible
> due to scale.
> 
> Some random stats may be useful as well:
> 
> - Number of connected peers that are SPV clients or full nodes (NODE_NETWORK)
> - Current block height (so that it's possible to detect stuck nodes)
> - Number of transactions in mempool
> - Number of transactions in UTXO set
> - Maybe some fee statistics,
> https://github.com/bitcoin/bitcoin/pull/3959 would be useful here
> - Number of orphan blocks/orphan transactions
> 
> Wladimir
> 
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Bitcoin-development mailing list
> [email-masked]
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development