Next: 1 Introduction 

Network Coordinates in the Wild

Network coordinates provide a mechanism for selecting and placing servers efficiently in a large distributed system. This approach works well as long as the coordinates continue to accurately reflect network topology. We conducted a long-term study of a subset of a million-plus node coordinate system and found that it exhibited some of the problems for which network coordinates are frequently criticized, for example, inaccuracy and fragility in the presence of violations of the triangle inequality. Fortunately, we show that several simple techniques remedy many of these problems. Using the Azureus BitTorrent network as our testbed, we show that live, large-scale network coordinate systems behave differently than their tame PlanetLab and simulation-based counterparts. We find higher relative errors, more triangle inequality violations, and higher churn. We present and evaluate a number of techniques that, when applied to Azureus, efficiently produce accurate and stable network coordinates. 

• 1 Introduction
• 2 Background
  • 2.1 Vivaldi
• 3 Latencies in the Wild
  • 3.1 Collection
  • 3.2 Round Trip Times
  • 3.3 Violations of the Triangle Inequality
  • 3.4 Dimensionality
  • 3.5 Intercontinental Latency Distributions
• 4 Taming Live Coordinate Systems
  • 4.1 Latency and Update Filters
  • 4.2 Neighbor Decay
• 5 Measuring Coordinate Systems
• 6 Internet-Scale Network Coordinates
  • 6.1 Refining Azureus' Coordinates
  • 6.2 PlanetLab Snapshots
  • 6.3 End-Host Live Coordinates
  • 6.4 Application-Level Performance
• 7 Barriers to Accuracy
  • 7.1 Churn
  • 7.2 Drift
  • 7.3 Intrinsic Error
  • 7.4 Corruption and Versioning
  • 7.5 Latency Variance
• 8 Related Work
  • 8.1 Network Coordinates
• 9 Conclusion
• 10 Acknowledgements
• Bibliography
• About this document ...