Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Mar 1996 18:55:06 -0800
From:      David Greenman <davidg@Root.COM>
To:        Hussein Kanji <hussein@verso.com>
Cc:        freebsd-questions@FreeBSD.org
Subject:   Re: Slow FTP & web rates/network speed 
Message-ID:  <199603210255.SAA04264@Root.COM>
In-Reply-To: Your message of "Wed, 20 Mar 1996 17:36:07 PST." <199603210136.RAA00221@server.verso.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
>We've got a Pentium 133 with 96 megs of memory and a SMC PCI Ethernet card
>hooked up to a T1. With that hardware, we'd imagine that ftp transfers
>should be flying... but no such luck.
>
>We have an anonymous FTP server set up on this machine and it takes care of
>about 5 hosts on the Web that are hit pretty hard. Running top, most of the
>memory gets cached for NCSA 1.5, but the system is about 98-99% idle. Each
>site sees about 100,000 hits/day.
>
>I've recompiled the kernel several times, with the following options
>
>        maxusers 256
>        nmbclusters=4096
>
>to get it to speed up (and cuz I thought I might have run out of mbufs).
>I've also had complaints that people are getting dropped connections on ftp
>and the transfer rates are really low. 
>
>Any ideas on how to speed things up? Please email them to me. Thanks.

   Switch service providers? TLG's traffic appears to go out MCI and MCI in
the Bay Area is *extremely* lossy right now. It's difficult to get more than a
few KBytes/second through MCI these days. They're planning on upgrading this
portion of their network to OC-3c/ATM (155Mbits), but until then, MCI just
sucks.
   Repeated traceroutes also seems to indicate that TLG's network is
overloaded.

[wcarchive:davidg] traceroute ftp.verso.com
traceroute to server.verso.com (140.174.164.180), 30 hops max, 40 byte packets
 1  F0-CRL-SFO-01-F0/0.US.CRL.NET (165.113.58.1)  4.590 ms  1.649 ms  1.359 ms
 2  pb.mci.net (198.32.128.12)  4.030 ms  3.422 ms  3.240 ms
 3  borderx1-hssi3-0.SanFrancisco.mci.net (204.70.158.105)  6.939 ms  7.125 ms  5.842 ms
 4  border1-fddi-0.SanFrancisco.mci.net (204.70.2.162)  8.695 ms  5.280 ms  3.774 ms
 5  * rgnet-b1-serial3-1.SanFrancisco.mci.net (204.70.32.50)  101.454 ms  196.865 ms
 6  ln1_gw2-mv-tlg_sf.tlg.net (140.174.192.2)  51.407 ms  71.436 ms *
 7  tlg-cust-link.tlg.net (140.174.26.10)  72.190 ms  84.071 ms *
 8  hi1.meer.net (140.174.164.180)  80.800 ms  76.546 ms  123.561 ms

[wcarchive:davidg] ttcp -p9 -n32 -t ftp.verso.com
ttcp-t: buflen=8192, nbuf=32, align=16384/+0, port=9  tcp  -> ftp.verso.com
ttcp-t: socket
ttcp-t: connect
ttcp-t: 262144 bytes in 111.36 real seconds = 2.30 KB/sec +++
                                              ^^^^^^^^^^^
   Yuck.
   In any case, the problem does not appear to be with FreeBSD.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603210255.SAA04264>