With non-compressed connections, acceleration adds options to the
packet’s TCP header, but leaves the packet payload intact. These options allow
the CloudBridge devices at each end of the connection to communicate with each
other. In addition, the TCP sequence number is adjusted to prevent routing
issues or appliance failure from mixing accelerated packets and non-accelerated
packets in the same connection.
With compressed connections, the payload is compressed, of course,
and the output of the compressor is accumulated into full-sized packets. The
upshot is that, for example, 3:1 compression results in one-third as many
packets being transmitted, rather than the same number of packets, each reduced
to one-third size. Compression also uses CloudBridge TCP header options and
sequence number adjustment.