You won't in the real world.
>using compression on a TCP/IP connection. Why would you _not_ want 2:1
>compression on a T-1 link? Whats the alternative - get another T1
Compression introduces latency. The more data you try to compress, the
worse it will get.
You will also eventually overwhelm the CPU. It is widely accepted that
trying to compress a full T1 is a *bad* idea.
>carrying traffic you can bill for. Now I know this is not a full T1 link,
>but you see the economic benefits of compression?
It doesn't work the same way on a line that is highly utilized. There are
know statistics on dialin usage, etc. You design for those. Trying to
deal with a full T1 that is stuffed full of data is different from dealing
with 23 B channels all being used by dialin users.
>a given pipe (compression) is a good economic deal. And this is
>independent of the size of the pipe - right?
It would raise the HW costs significantly to give it the kind of horsepower
needed. And it would introduce latency - which is the bane of any
interactive application. Latency is the number one problem for gaming for
instance.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588