From owner-freebsd-isp Wed Apr 7 13:19:48 1999 Delivered-To: freebsd-isp@freebsd.org Received: from tahoe.cinenet.net (ns1.cinenet.net [198.147.76.65]) by hub.freebsd.org (Postfix) with ESMTP id 224941589C for ; Wed, 7 Apr 1999 13:19:39 -0700 (PDT) (envelope-from sraja@cinenet.net) Received: from hollywood.cinenet.net (hollywood.cinenet.net [198.147.76.75]) by tahoe.cinenet.net (8.8.6/8.8.6) with ESMTP id NAA24345 for ; Wed, 7 Apr 1999 13:17:36 -0700 (PDT) Received: from localhost (sraja@localhost) by hollywood.cinenet.net (SMI-8.6/) with SMTP id NAA13817 for ; Wed, 7 Apr 1999 13:17:35 -0700 X-Authentication-Warning: hollywood.cinenet.net: sraja owned process doing -bs Date: Wed, 7 Apr 1999 13:17:35 -0700 (PDT) From: Suresh Rajagopalan To: freebsd-isp@freebsd.org Subject: NFS slowness on 100 LAN Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am seeing very slow response over NFS between a 3.1 client and Solaris X86 NFS server, with both NIC's set to 100M-FD. Writing a 2MB file takes 30 seconds. Some data points: 1. The NIC card is a 3COM, and the ifconfig options are set to use "media 100BaseT mediaopt full-duplex" 2. Mount options set to tcp, nfsv3. (udp or nfsv2 don't work either and cause system hangs). 3. If the 3.1 client is slowed down to 10MB-FD, then writing the same file much faster, a typical response of under 1 second. 4. The same slow behaviour is seen when accessing a FreeBSD NFS server, (although this is a 2.2.6 box). 5. The switch is a 3COM Superswitch, with ports forced to 10FD or 100FD, depending on the machine (autonegotiate is off). Attempting this with a Intel Pro100 shows the same behaviour. Thanks for any help, Suresh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message