home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!agate!ames!cronkite.cisco.com!tli
- From: tli@cisco.com (Tony Li)
- Newsgroups: comp.dcom.sys.cisco
- Subject: Re: re:ip tcp header-compression experience
- Date: 25 Jan 1993 10:03:19 GMT
- Organization: cisco Systems, Menlo Park, California, USA
- Lines: 25
- Message-ID: <1k0dt8INN8h@cronkite.cisco.com>
- References: <727810442.26482@news.Colorado.EDU> <OLAV.KVITTEM.93Jan25102536@delab.sintef.no>
- NNTP-Posting-Host: lager.cisco.com
-
- In article <OLAV.KVITTEM.93Jan25102536@delab.sintef.no> Olav.Kvittem@delab.sintef.no writes:
- What about higher speed links - how fast can a cisco run
- TCP Header compression - can it be done on 512 Kbps links and
- if so - what CPU-size is needed ?
-
- My tests (under lab conditions) show that we could saturate a 72k link
- doing an FTP (i.e., big packets) and consume about 10% of a CSC/3. This
- would suggest that a single 512K link would pretty well consume a CSC/3.
- You might get away with it with a CSC/4.
-
- However, I'm not convinced that this is going to be a significant win.
- Header compression provides the biggest advantage if you're using lots of
- small packets (i.e., telnet sessions).
-
- Does the number of simultanesous sessions have to be limited to
- allow any effect ?
-
- Yes. Header compression only can cache up to 254 (default 16) connections.
-
-
- --
- abyss \*-'bis\ n
- 1 : the bottomless gulf, pit, or chaos of the old cosmogonies 2 a : an
- immeasurably deep gulf or great space b : intellectual or spiritual
- profundity; also : vast moral depravity 3 a Border Intermediate System
-