-
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 less than 1/5 packets of HTTP/1.0
-
Cache load may use less than 1/2 packets of HTTP/1.0
-
HTTP/1.1 up to twice as fast as HTTP/1.0 (elapsed time)
-
Server also gains when using pipelining
-
Client implementation required some care and effort; server implementation
was very easy, though slight care in output buffering makes a significant
difference in performance
-
Nagle is not a bottleneck
-
Recommend that it is turned off