From owner-freebsd-current Wed Dec 4 12:39:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA05139 for current-outgoing; Wed, 4 Dec 1996 12:39:38 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA05094 for ; Wed, 4 Dec 1996 12:39:34 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA11433; Wed, 4 Dec 1996 13:38:31 -0700 (MST) Date: Wed, 4 Dec 1996 13:38:31 -0700 (MST) Message-Id: <199612042038.NAA11433@rocky.mt.sri.com> From: Nate Williams To: Nate Williams Cc: Doug Rabson , current@freebsd.org Subject: Re: nfs v2 In-Reply-To: <199612041926.MAA11255@rocky.mt.sri.com> References: <199612041538.CAA01116@asstdc.scgt.oz.au> <199612041926.MAA11255@rocky.mt.sri.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > FWIW, I just tried mounting a 2.1.6.1 FS onto a 2.2 box and have no > problems. Unfortunately, I can't easiily mount a 2.1.6.1 FS from a > -current machine since my -current box is also my 2.1.6.1 box (my laptop > has two disks). More on the 2.1.6.1 vs. 2.2 boxes: - Stock configuration for nfs_client/server setups. - Nec is a NEC P/75 laptop with 3C589 ethernet and 24MB of memory - Spider is a ThinkPad P/75 laptop with 3C589 ethernet and 24MB of memory NEC is running 2.1.6.1 and reading from a 2.2 server. nec:/nfs/spider # uname -a FreeBSD nec.mt.sri.com 2.1.6.1-RELEASE FreeBSD 2.1.6.1-RELEASE #0: Wed Dec 4 12:53:29 MST 1996 nate@nec.mt.sri.com:/usr/src/sys/compile/CARD i386 nec:/nfs/spider # iozone ... Writing the 1 Megabyte file, 'iozone.tmp'...7.273438 seconds Reading the file...20.265625 seconds IOZONE performance measurements: 144165 bytes/second for writing the file 51741 bytes/second for reading the file And here spider is running 2.2 and reading from a 2.1.6.1 server spider:/nfs/nec # uname -a FreeBSD spider.mt.sri.com 2.2-RELEASE FreeBSD 2.2-RELEASE #4: Wed Dec 4 11:17:07 MST 1996 nate@spider.mt.sri.com:/usr/src/sys/compile/INCON i386 spider:/nfs/nec # iozone ... Writing the 1 Megabyte file, 'iozone.tmp'...7.750000 seconds Reading the file...1.062500 seconds IOZONE performance measurements: 135300 bytes/second for writing the file 986895 bytes/second for reading the file It's pretty obvious to me that somehow the 2.2 server is either not serving very well, or the 2.1.6.1 client isn't reading very well. But, if I use a Solaris 2.5 server for both, the 2.1.6.1 client still sucks rocks on reading. nec:/nfs/rocky # iozone Writing the 1 Megabyte file, 'iozone.tmp'...2.968750 seconds Reading the file...19.703125 seconds IOZONE performance measurements: 353204 bytes/second for writing the file 53218 bytes/second for reading the file And, the 2.2 client really rocks using the Solaris server: spider:/nfs/rocky # iozone Writing the 1 Megabyte file, 'iozone.tmp'...3.117188 seconds Reading the file...1.023438 seconds IOZONE performance measurements: 336385 bytes/second for writing the file 1024562 bytes/second for reading the file And, just to throw a wrench into the works: Server: (p100-32MB of memory and a DEC-PCI ethernet card) FreeBSD moth.mt.sri.com 2.2-CURRENT FreeBSD 2.2-CURRENT #15: Fri Jun 7 23:00:27 MDT 1996 nate@moth.sri.MT.net:/usr/src/sys/compile/DMOTH i386 (It's running a *really* old version of -current). 2.1.6.1 client: Writing the 1 Megabyte file, 'iozone.tmp'...4.218750 seconds Reading the file...3.968750 seconds IOZONE performance measurements: 248551 bytes/second for writing the file 264208 bytes/second for reading the file At least we have decent read speed: 2.2 client: Writing the 1 Megabyte file, 'iozone.tmp'...3.648438 seconds Reading the file...0.921875 seconds IOZONE performance measurements: 287404 bytes/second for writing the file 1137438 bytes/second for reading the file Write speed isn't quite up to the Solaris box, but read speed is better. I'm pretty happy with the 2.2 boxes, but the performance of the 2.1.6.1 client is *really* bad. Nate