比较了根DNS与CDN的任播延迟差异，指出两者应采用不同优化策略。
Anycast Performance in Context
- 构建对比延迟模型，分析任播在不同场景下的路径膨胀机制
- 根DNS可容忍较大路径膨胀而用户感知延迟低，CDN则需严格控制延迟
- 提出分离容错与延迟目标的优化框架，适合不同服务场景
IP任播允许服务从多个物理站点发布同一地址，由BGP将客户端路由至最近站点。它在根DNS服务器系统、公共解析器及部分内容分发网络中至关重要，但相同路由机制在不同应用中表现迥异。本文比较了根DNS与CDN场景下的任播延迟：根DNS通过递归缓存将根服务器延迟分摊至大量用户和长生存期（TTL），而CDN中每轮往返直接影响页面加载、视频启动或API延迟。研究发现，根DNS任播虽存在显著路径膨胀，用户感知延迟仍有限；而CDN任播需主动优化对等互联、路由策略、覆盖范围和测量反馈以控制膨胀。论文贡献包括一个对比延迟模型、可复现的测量设计及分离容错与延迟目标的优化框架。核心结论为：根DNS与CDN不应使用相同优化目标函数——前者以鲁棒性、可达性和缓存行为为主导，后者则关注尾部延迟、覆盖正确性和策略控制。
原文摘要 · Abstract (English)
IP anycast lets a service advertise one address from many physical sites, leaving BGP to map each client to a site. It is central to the DNS root server system, public resolvers, and some content delivery networks, yet the same routing mechanism has very different consequences across applications. This paper compares anycast latency in two settings: root DNS, where recursive caching amortizes root-server delay over many users and long time-to-live values, and CDNs, where each additional round trip can directly affect page-load, video-start, or API latency. The synthesis finds that root DNS anycast can exhibit substantial path inflation while still producing limited user-visible delay, whereas CDN anycast requires active engineering of peering, route policy, catchment scope, and measurement feedback to keep inflation small. The paper contributes a comparative latency model, a reproducible measurement design, and an optimization framework that separates resilience-driven anycast objectives from latency-driven objectives. The central conclusion is practical: operators should not optimize root DNS and CDN anycast with the same objective function. For root DNS, robustness, reachability, and cache behavior dominate; for CDN services, tail latency, catchment correctness, and policy control dominate.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品；中文卡片由大模型生成，请以原文为准。