3 ms·

All the blockchain is local. The time taken to resolve a key->value pair is the time your software takes to decode information from your disk; it's nothing comp

by rakoo 13y ago

All the blockchain is local. The time taken to resolve a key->value pair is the time your software takes to decode information from your disk; it's nothing compared to DNS. Change propagation, on the other hand, is as long as blocks can travel from peer to peer.

VikingCoder 13y ago
Hmm - if your ISP has a good DNS, and has a cache hit on your DNS request, versus if you have to seek your HD, the DNS might be much, much faster. http://www.eecs.berkeley.edu/~rcs/research/interactive_latency.html http://www.eecs.berkeley.edu/~rcs/research/interactive_laten... Round trip in same datacenter: 500,00ns. Disk seek: 4,000,000ns. You have to lean on the numbers pretty hard to make the DNS faster, but it's possible it could be faster than your local disk.
- al2o3cr 13y ago
  Pretty sure the intersection of the set of people who worry about DNS performance and the set of people who are still running servers exclusively off spinning rust is nigh-vanishing...
- ferongr 13y ago
  The broadband connection usually has latency depending on the protocol. ADSL2+ with data interleaving can be as high as 32ms. DOCSIS has at least 5ms for the first hop too. And that assumes your ISP's (or whichever) DNS server is close from a network perspective and that it has enough power to instantly send a reply down the wire.