From owner-freebsd-current Sun Mar 12 14: 9:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id CCB6E37BD17 for ; Sun, 12 Mar 2000 14:09:44 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA73609; Sun, 12 Mar 2000 14:09:38 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38CC15A2.C7EB350@gorean.org> Date: Sun, 12 Mar 2000 14:09:38 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-CURRENT-0307 i386) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?J=E9rome?= OUFELLA Cc: freebsd-current@freebsd.org Subject: Re: 3.4 vs. 4.0 NFS Code performance References: <38C8D3BE.15F17D29@esil.univ-mrs.fr> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jérome OUFELLA wrote: > > Hi, > > I need to use a quite big NFS server, serving ~120GB for ~200 > clients, all OS's mixed (*BSD, Linux, HP-UX, IRIX, Solaris, Xterminals). > > Is it worth it to use the -current branch (-release on next monday > perhaps?) for this important server, or should I rather use the > 3.4-STABLE NFS implementation ? For heavy NFS use I wouldn't consider anything else. We've had September-vintage 4.0-current (as in, right after the big NFS fixes went in) machines in production and never had problems with them. We're getting ready to go to 4.0-Release when we get a chance. I'm already using it for other things. That said, you shouldn't expect 4.0-Release to be like a -Stable branch, not yet anyway. Be ready to live up to the usual -current responsibilities, like following this list, etc. Good luck, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message