Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!helios.ee.lbl.gov!pasteur!ucbvax!dsacg3.dsac.dla.mil!ntm1569
From: ntm1569@dsacg3.dsac.dla.mil (Jeff Roth)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Throughput from MILNET
Message-ID: <8912141729.AA07931@dsacg3.dsac.dla.mil>
Date: 14 Dec 89 17:29:36 GMT
References: <137598.8912131631@asd.wpafb.af.mil>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jroth@dsac.dla.mil (Jeff Roth)
Organization: Defense Logistics Agency Systems Automation Center, Columbus
Lines: 15


I've also been unpleasantly surprised by both throughput and
latency on the network. Our studies have shown some variation
by time of day but not as much as you might suspect; there is
greater variation depending on the route the data takes. It's
likely overloaded PSNs, in fact our worst cases are going
through one PSN to another at the same site (WPAFB).

But it does appear 56 KB buys you something; our FTP
throughput, using a 9.6 circuit, is more like 1 KB/s at best.

By the way I'd appreciate it if any readers with information on
what if any, plans exist to upgrade Milnet capacity could point
me to a source (or let me know privately by email what we can
expect).