Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!mit-eddie!genrad!decvax!ucbvax!MIT-MULTICS.ARPA!Kodinsky
From: Kodinsky@MIT-MULTICS.ARPA
Newsgroups: comp.protocols.tcp-ip
Subject: Re: tcp/ip/IBM/ProNET
Message-ID: <870502144215.703428@MIT-MULTICS.ARPA>
Date: Sat, 2-May-87 10:42:00 EDT
Article-I.D.: MIT-MULT.870502144215.703428
Posted: Sat May  2 10:42:00 1987
Date-Received: Tue, 5-May-87 00:46:56 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 26

Speeds iun excess of 100 Kbytes/Second are not unheard of for TCP/IP on
VM.  Using KNET/VM on a VM system (true it is a 3090/200) I have seen
speeds peak at about 150 Kbytes/sec.  With averages about 85 or 90.
Also, this was not sunday mornging, but the middle of a weekday
afternoon.  Other KNET/VM users have reported peaks above 100 Kbytes/sec

Also at spartacus we have peaked at about 55 Kbytes per secoond -
running on a Nixdorf 8890/50 (4331 level machine) and all of our
terminals and disk drives on the same channel - and only one head of
string unit for our disks (for the non S/370 people read that as
extreeeeeemellly sloooooooowwwwwwww).

Now I admit a biased point of view (I am the KNET/VM Development
Manager) and the above is not the full story - on our system during the
middle of the day at abd load times (command response times on the order
of 10's of seconds) I have seen rates drop below 1Kb/second.

My point is that 100KB/Sec has been broken, with production, generally
available products, on production systems experiencing production loads
(not overloads!!!!!).

One final caveat - the speeds that other KNET users may see depend on
many variables and the above speeds should not be used as a guarantee of
the speeds you see ("The milage you get may vary....").

Frank Kastenholz Manager, KNET/VM Development Spartacus/Fibronics