From owner-freebsd-current Thu Oct 28 13: 3:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 79AD914D03 for ; Thu, 28 Oct 1999 13:03:12 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA22741; Thu, 28 Oct 1999 13:03:07 -0700 Date: Thu, 28 Oct 1999 13:03:11 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: really draggy NFS access in -current? In-Reply-To: <14360.43601.640725.402212@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG UDP. Local network. Very puzzling. On Thu, 28 Oct 1999, Andrew Gallatin wrote: > > Matthew Jacob writes: > > > > Hmm. Could be. That's a good thing to try. The connection is a Full Duplex > > 100BaseT to a 3com switch (both alpha/freebsd && Solaris) so what you > > suggest Just Didn't Occur To Me (tm). Thanks.... > > > > Is this a UDP or TCP mount? > > I've seen very strange things with TCP mounts of Solaris 2.7 servers > with i386 clients running recent -currents. Things start out just > fine (3-4MB/sec), then after some period of time (a day or 2 > generally), the performance degrades down to a few KB/sec. > > I didn't really have time to look into it properly, so I just switched > all my mounts over to udp & the problem just went away. > > Drew > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message