From owner-freebsd-hackers Sun Aug 27 00:34:58 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id AAA11835 for hackers-outgoing; Sun, 27 Aug 1995 00:34:58 -0700 Received: from aries.ibms.sinica.edu.tw ([140.109.40.248]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id AAA11829 for ; Sun, 27 Aug 1995 00:34:54 -0700 Received: (from taob@localhost) by aries.ibms.sinica.edu.tw (8.6.11/8.6.9) id PAA06512; Sun, 27 Aug 1995 15:33:41 +0800 Date: Sun, 27 Aug 1995 15:33:41 +0800 (CST) From: Brian Tao To: Christopher Sedore cc: "Amancio Hasty Jr." , freebsd-hackers@freebsd.org Subject: Re: Making a FreeBSD NFS server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@freebsd.org Precedence: bulk On Wed, 23 Aug 1995, Christopher Sedore wrote: > > The Network Computing article test were done over FDDI. I got ~3MB/sec > write and ~2MB/sec read while doing the tests. > > Note that the ~2MB/sec read was from a disk which only yielded ~2MB/sec > when using IOZone locally, so a 7200 rpm drive may make the number go up. I mounted a local disk via NFS through the loopback interface (after being reminded that the hostname list to mount(8) isn't comma- delimited ;-)) and got 1.4 MB/s reading and 1.8 MB/s writing (with async NFS writes). Running iozone directly on that disk gets me about 3.9 MB/s read and write. My test machine is a 486DX4/100, so it sounds like a Pentium was used in your benchmark. > As I understand some of the NFS protocol issues, you probably won't see > more than ~2MB/sec read from a single process anyway, so you'd have to use > multiple IOZones or whatever other benchmark you use to break that barrier. I'd like to see how FreeBSD holds up in an environment where there are 100+ users all trying to read/write to home directories that are located on a central fileserver. -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org