Bitcoin Forum
June 14, 2024, 07:22:50 PM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin Network Metrics  (Read 895 times)
MatthewLM (OP)
Legendary
*
Offline Offline

Activity: 1190
Merit: 1004


View Profile
August 28, 2012, 11:31:48 PM
 #1

Does anyone have any data on:

1. The average latency of a connection.
2. The average data transfer rate of a connection.
3. Average number of lost connections per time of connection.
4. Percentage of transactions in new blocks, up-to-date nodes already have.

I'm trying to calculate the benefit of the proposal here: https://en.bitcoin.it/wiki/User:MatthewLM/ImprovedBlockRelayingProposal

The proposal increases latency but increases parallelism and removes redundancy. It may increase or decrease bandwidth usage depending upon the amount of redundancy saved vs the additional overhead.

Jeff Garzik seems to think that latency is the biggest problem when downloading blocks and additional latency would make things slower. Is there data to support this? Of-course, I'm considering the future: when block sizes could grow into several MBs and beyond. Shouldn't we prepare changes for this now?
zvs
Legendary
*
Offline Offline

Activity: 1680
Merit: 1000


https://web.archive.org/web/*/nogleg.com


View Profile WWW
August 30, 2012, 09:27:37 PM
 #2

Does anyone have any data on:

1. The average latency of a connection.
2. The average data transfer rate of a connection.
3. Average number of lost connections per time of connection.
4. Percentage of transactions in new blocks, up-to-date nodes already have.

I'm trying to calculate the benefit of the proposal here: https://en.bitcoin.it/wiki/User:MatthewLM/ImprovedBlockRelayingProposal

The proposal increases latency but increases parallelism and removes redundancy. It may increase or decrease bandwidth usage depending upon the amount of redundancy saved vs the additional overhead.

Jeff Garzik seems to think that latency is the biggest problem when downloading blocks and additional latency would make things slower. Is there data to support this? Of-course, I'm considering the future: when block sizes could grow into several MBs and beyond. Shouldn't we prepare changes for this now?
Maybe 6 months ago... latency is much less of an issue now with the increase in size of the blocks.   A dial-up connection has about 120-150ms base latency (transfer speed, ~5kB/s), a satellite connection approaching 1000ms (can reach 100kB/s+ easily)....  If you're transferring anything over, uh, 30kB, it seems to me like it would be preferable to connect to the person using the satellite connection.  It's not something that would require a lot of ACKs (like, say, online gaming)

Umm, I have some log files that may be useful, I've been running with around 900 connections
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!