Network performance effects of HTTP/1.1, CSS1, and PNG

ABSTRACT

We describe our investigation of the effect of persistent connections, pipelining and link level document compression on our client and server HTTP implementations. A simple test setup is used to verify HTTP/1.1's design and understand HTTP/1.1 implementation strategies. We present TCP and real time performance data between the libwww robot [27] and both the W3C's Jigsaw [28] and Apache [29] HTTP servers using HTTP/1.0, HTTP/1.1 with persistent connections, HTTP/1.1 with pipelined requests, and HTTP/1.1 with pipelined requests and deflate data compression [22]. We also investigate whether the TCP Nagle algorithm has an effect on HTTP/1.1 performance. While somewhat artificial and possibly overstating the benefits of HTTP/1.1, we believe the tests and results approximate some common behavior seen in browsers. The results confirm that HTTP/1.1 is meeting its major design goals. Our experience has been that implementation details are very important to achieve all of the benefits of HTTP/1.1.For all our tests, a pipelined HTTP/1.1 implementation outperformed HTTP/1.0, even when the HTTP/1.0 implementation used multiple connections in parallel, under all network environments tested. The savings were at least a factor of two, and sometimes as much as a factor of ten, in terms of packets transmitted. Elapsed time improvement is less dramatic, and strongly depends on your network connection.Some data is presented showing further savings possible by changes in Web content, specifically by the use of CSS style sheets [10], and the more compact PNG [20] image representation, both recent recommendations of W3C. Time did not allow full end to end data collection on these cases. The results show that HTTP/1.1 and changes in Web content will have dramatic results in Internet and Web performance as HTTP/1.1 and related technologies deploy over the near future. Universal use of style sheets, even without deployment of HTTP/1.1, would cause a very significant reduction in network traffic.This paper does not investigate further performance and network savings enabled by the improved caching facilities provided by the HTTP/1.1 protocol, or by sophisticated use of range requests.

REFERENCES

• 1: Venkata N. Padmanabhan , Jeffrey C. Mogul, Improving HTTP latency, Computer Networks and ISDN Systems, v.28 n.1-2, p.25-35, Dec. 1995 [doi>10.1016/0169-7552(95)00106-1]
• 2: Nagle, J., "Congestion Control in IPFfCP Intemetworks," RFC 896, Ford Aerospace and Communications Corporation, January 1984.
• 3: Bemers-Lee, Tim, R. Fielding, H. Frystyk. "Informational RFC 1945- Hypertext Transfer Protocol-- HTrPI1.0," MIT/LCS, UC Irvine, May 1996.
• 4: Fielding, R., J. Gettys, J.C. Mogul, H. Frystyk, T. Bemers- Lee, "RFC 2068 - Hypertext Transfer Protocol -- HTrP/1.I," UC Irvine, Digital Equipment Corporation, MIT.
• 5: Touch, J., J. Heidemann, K. Obraezka, "Analysis of HTTP Performance," USC/Information Sciences Institute, June, 1996.
• 6: Spero, S., "Analysis of HTrP Performance Problems," http://www, w3.or~dl:'rotocol~/1.O/HTrPPerformance.html July 1994.
• 7: John Heidemann, Performance interactions between P-HTTP and TCP implementations, ACM SIGCOMM Computer Communication Review, v.27 n.2, p.65-73, Apr. 1997 [doi>10.1145/263876.263886]
• 8: T. J. Shepard, TCP PACKET TRACE ANALYSIS, Massachusetts Institute of Technology, Cambridge, MA, 1991
• 9: Mogul, J, 'The Case for Persistent.Connection HTrP", Western Research Laboratory Research Report 95/4, http://www,research.digital.com/wrl/publicationsgabstracts195.4. lltml, Digital Equipment Corporation, May 1995.
• 10: Lie, H., B. Bos, "Cascading Style Sheets, level 1," W3C Recommendation, World Wide Web Consortium, 17 Dec 1996.
• 11: V. Jacobson, Congestion avoidance and control, Symposium proceedings on Communications architectures and protocols, p.314-329, August 16-18, 1988, Stanford, California, United States
• 12: Postel, Jon B., "Transmission Control Protocol," RFC 793, Network Information Center, SRI International, September 1981.
• 13: Paxson, V., "Growth Trends in Wide-Area TCP Connections," IEEE Network, Vol. 8 No. 4, pp. 8-17, July 1994.
• 14: Jacobson, V., C. Leres, and S. McCanne, tcpdump, available at flp://ftp.ee.lbl.gov/tcpdump.tar. Z.
• 15: Robert W. Scheifler , Jim Gettys, The X window system, ACM Transactions on Graphics (TOG), v.5 n.2, p.79-109, April 1986 [doi>10.1145/22949.24053]
• 16: Manasse, Mark S., and Greg Nelson, "Trestle Reference Manual," Digital Systems Research Center Research Report # 68, December 1991.
• 17: Braden, R., "Extending TCP for Transactions -- Concepts," RFC-1379, USC/ISI, November 1992.
• 18: Braden, R., "T/TCP -- TCP Extensions for Transactions: Functional Specification," RFC-1644, USC~SI, July 1994.
• 19: Touch, J., "TCP Control Block Interdependence," RFC 2140, USC/ISI, April 1997.
• 20: Boutell, 7'., T. Lane et. al. "PNG (Portable Network Graphics) Specification," W3C Recommendation, October 1996, RFC 2083, Boutell. Com Inc., January 1997. http://www, w3.org/pub/WW /Graphics/PNG has extensive PNG information.
• 21: Ryan, M., tcpshow, I.T. NetworX Ltd., 67 Men'ion Square, Dublin 2, ireland, June 1996.
• 22: Deutsch, P., "DEFLATE Compressed Data Format Specification version 1.3," RFC 1951, Aladdin Enterprises, May 1996,
• 23: Deutsch, L. Peter, Jean-Loup Gailly, "ZLIB Compressed Data Format Specification version 3.3," RFC 1950, Aladdin Enterprises, Info-ZIP, May 1996.
• 24: "Recommendation V.42bis (01/90- Data Compression procedures for data circuit terminating equipment (DCE) using error correction procedures," ITU, Geneva, Switzerland, January 1990,
• 25: Online summary of results and complete data can be found at http:liwww, w3.orgli:'rotocols/HTrPlPefformancel.
• 26: Jeffrey C. Mogul , Fred Douglis , Anja Feldmann , Balachander Krishnamurthy, Potential benefits of delta encoding and data compression for HTTP, Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication, p.181-194, September 14-18, 1997, Cannes, France
• 27: Nielsen, Henrik Frystyk, "Libwww- the W3C Sample Code Library," World Wide Web Consortium, April 1997. Source code is available at http://www.w3.org/Library.
• 28: Baird-Smith, Anselm, "Jigsaw: An object oriented server," World Wide Web Consortium, February 1997. Source and other information are available at http:/Avww.w3.org/Jigsaw.
• 29: The Apache Group, "The Apache Web Server Project." The Apache Web server is the most common Web server on the Internet at the time of this paper's publication. Full source is available at http://www.apache, org.
• 30: A Web page pointing to style sheet information in general can be found at http://www.w3.org/StyleL
• 31: Multiple-image Network Graphics Format (MNG), version 19970427. ftp:llswrinde.nde.swri.edulpublmngldocumentsldraftmng-19970427.html.

INDEX TERMS

Primary Classification:
  C. Computer Systems Organization
  C.2 COMPUTER-COMMUNICATION NETWORKS

Additional Classification:
  H. Information Systems
  H.3 INFORMATION STORAGE AND RETRIEVAL

  I. Computing Methodologies
  I.7 DOCUMENT AND TEXT PROCESSING

General Terms:
Design, Documentation, Performance