页面性能、keepalive等.ppt

Whole Page Performance Leeann Bent and Geoffrey M. Voelker University of California, San Diego Whole Page Performance? Extensive previous work on how specific techniques affect individual object download. Caching, Prefetching, CDNs, DNS caching. However, user downloads pages of objects. Not clear how individual object performance maps onto whole page performance Goal: Study whole page performance Extent to which different optimizations are used Effect on downloading whole pages of objects Related Work [Krishnamurthy and Wills99] look at: Parallel (HTTP1.0), persistent and pipelined connections. In addition to caching, range requests, and content placed on different servers. Top-level pages of popular sites. Focus on pages where all optimizations used. Our Study: Follow on, with a different perspective. Use real user workloads. All pages, not just top level pages on popular servers Not all pages use optimizations Base page + embedded objects. Connection optimizations + CDNs + DNS. Overview Introduction Methodology Results Conclusion Methodology Overview Use Medusa to: Record everyday browsing from six users over four days. Replay traces toggling performance options: Parallel Connections Using CDNs Complete DNS caching Persistent Connections Compute download costs for whole pages The Medusa Proxy Page Download Time Page download time Time required to download base page and all embedded objects. Reflects user-perceived web performance Calculated using object download time. Determine object download time from just after DNS lookup to connection close or full object return (persistent). Incorporate original recorded DNS times where appropriate. Example Traces Six users: April 27 - 30 (Sat. - Tues.). Originally 22,228 objects and 1,455 pages. Remove error pages. Replay data gathered May 6-7 (Mon - Tues) June 22-27 (Sat. – Thurs.). Minimize warming effects by taking median of 5 consecutive page downloads. Optimization Combinations Parallel Connections (1) Medusa t