From owner-freebsd-current Wed Dec 15 11:22:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 23275155E1 for ; Wed, 15 Dec 1999 11:22:36 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id OAA02120; Wed, 15 Dec 1999 14:22:34 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA19135; Wed, 15 Dec 1999 14:22:03 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 15 Dec 1999 14:22:03 -0500 (EST) To: Matthew Dillon Cc: freebsd-current@freebsd.org Subject: Re: Serious server-side NFS problem In-Reply-To: <199912151912.LAA40369@apollo.backplane.com> References: <14423.46117.353932.473968@grasshopper.cs.duke.edu> <199912151912.LAA40369@apollo.backplane.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14423.59494.219984.475675@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > > :Also, while read performance has improved by 44%, write performance > :has degraded by between 50 - 70% (FreeBSD clients)! Here are some > :quick benchmarks. Note that the file size of 512MB is larger than > :memory on both the server and client. Also note that the disk array > :on the server will read at 50MB/sec and write at 40MB/sec, so we are > :not disk bound ;-) > : > :- UDP NFS write performance from a FreeBSD client: > : > :July's kernel: > :% dd if=/dev/zero of=zot bs=1024k count=512 > :512+0 records in > :512+0 records out > :536870912 bytes transferred in 52.780773 secs (10171714 bytes/sec) > : > :Today's kernel:: > :% dd if=/dev/zero of=zot bs=1024k count=512 > :512+0 records in > :512+0 records out > :536870912 bytes transferred in 141.593458 secs (3791636 bytes/sec) > > Question on these: Is it the client you are running the old and new > kernels on or the server? Also, make sure you are running the same > number of nfsiod's on each (and also try running a different number > of nfsiod's). > > At the moment I am assuming you ran these tests with the client running > the old and new kernel. I have some ideas there in regards to inefficient > context switching when the nfsiod's are saturated that I am testing. > > -Matt Sorry I wasn't clear. The variable was the server's kernel version. The client's kernel remained constant. It was from sources built late week. When you are measuring server write performance, are you looking at the numbers from the client's perspective, or are you looking at the numbers from the point of view of the server's disks. I ask because if I watch the server via systat, I see a steady 10-11MB/sec hitting the disk. However, if I time the process, or look at the output from dd, I see the poor (< 4MB/sec) numbers I reported. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message