Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!FTP.COM!jbvb
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Performance of the PD Packages
Message-ID: <9104052046.AA12172@ftp.com>
Date: 5 Apr 91 20:46:29 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jbvb@ftp.com
Organization: The Internet
Lines: 31


    >>Machine1:  DOS, 386/25, WD8003e, KA9Q software
    >>Machine2:  Xenix, 386/20, Excelan Board, Excelan TCP/IP package.
    >>FTP put from 1 to 2 = 70KB/sec.
    >>FTP put from 2 to 1 = 10KB/sec.
    
    The PC is a Dell 310 20 MHz 386 clone with 8 megs memory and a 16 msec
    IDE disk, using Hyperdisk cache. Ethernet card is a WD 8003E.
     
    The Vax is some sort of recent miaco-Vax (3500????) running the current
    VMS. The MIPS is a MIPS 120.
    
    ... using NCSA Ftpbin on the PC here and transferring a 675 kilobyte file.

    send to VAX:                71 kilobytes/sec
    get from VAX to a file:     53 kilobytes/sec
    get from VAX to nul:        64 kilobytes/sec
    
    send to MIPS:               97 kilobytes/sec
    get from MIPS to a file:   107 kilobytes/sec
    get from MIPS to nul:      128 kilobytes/sec
    
With PC/TCP 2.05, running on a WD8003/A in a 16Mhz Model 80, with the default
number of packet buffers (5) and a 4Kb TCP window, talking to a Sun 386i on
the same Ethernet, I can FTP files from disk to null device in either
direction at about at 205Kb/sec.  The more the disk matters in a benchmark
of this sort, the less reliable it is; I don't know how fragmented either
end of a reported transfer is...

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901