- Roughly half of the packets in HTTP/1.0 are TCP open/close
- Such packets are not "congestion controlled"
- Significant further gain by using buffering with pipelining
- Validation may use as little as than 1/10 the packets of HTTP/1.0
- Cache load may use less than 1/2 packets of HTTP/1.0
- The mean size of a packet doubled in our tests
- The mean number of packets in a TCP session increased between
a factor of 2 and 10. This is less than one might naively expect, and is
due to buffering that reduces the number of packets/session.
- HTTP/1.1 is up to twice as fast as HTTP/1.0 (elapsed time)
- Server performance also gains when using pipelining
- Transport compression saved significant bandwidth
- Recommend that Nagle is turned off
