Re: TO COMPRESS OR NOT TO CMPRS (please reply)

Kent Fitch <Kent.Fitch@its.csiro.au> Sat, 22 February 1997 01:51 UTC

Received: from cnri by ietf.org id aa25812; 21 Feb 97 20:51 EST
Received: from portal.ex.tis.com by CNRI.Reston.VA.US id aa29165; 21 Feb 97 20:51 EST
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id UAA15941 for ipsec-outgoing; Fri, 21 Feb 1997 20:41:36 -0500 (EST)
Date: Sat, 22 Feb 1997 12:45:42 +1100
From: Kent Fitch <Kent.Fitch@its.csiro.au>
X-Sender: fit106@commsun
Reply-To: Kent Fitch <Kent.Fitch@its.csiro.au>
To: ipsec@tis.com
Subject: Re: TO COMPRESS OR NOT TO CMPRS (please reply)
Message-ID: <Pine.GSO.3.93.970222122545.2059A-100000@commsun>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

The W3C recently published an interesting note on the Network Performance
Effects of HTTP/1.1, Cascading Style Sheets and PNG image formats which 
may provide more information for this debate: 

 http://www.w3.org/pub/WWW/Protocols/HTTP/Performance/Pipeline.html

HTTP is a major component of my organization's WAN traffic, although maybe
it is not signficant for everyone.  Their study of HTTP/1.0 -v- HTTP/1.1
shows that signficiant reductions in packets, bytes and response time can
be expected using a persistent connection, pipelining requests on that
connection.  Compressing HTML in the application using zlib yielded a
further small improvement. Using PNG rather than GIF was estimated as
reducing payloads only slightly, but the ability to replace many images
with style sheet markup provided much bigger benefits.


Kent Fitch                           Ph: +61 6 276 6711
ITS  CSIRO  Canberra  Australia      kent.fitch@its.csiro.au