From owner-freebsd-stable@FreeBSD.ORG Mon Nov 28 05:24:37 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7DAD16A420 for ; Mon, 28 Nov 2005 05:24:36 +0000 (GMT) (envelope-from mse_software@charter.net) Received: from mxsf02.cluster1.charter.net (mxsf02.cluster1.charter.net [209.225.28.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EAF943D8A for ; Mon, 28 Nov 2005 05:24:20 +0000 (GMT) (envelope-from mse_software@charter.net) Received: from mxip07a.cluster1.charter.net (mxip07a.cluster1.charter.net [209.225.28.137]) by mxsf02.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id jAS5OHLi016111 for ; Mon, 28 Nov 2005 00:24:17 -0500 Received: from 68-116-0-143.dhcp.knwk.wa.charter.com (HELO yak.mseubanks.net) ([68.116.0.143]) by mxip07a.cluster1.charter.net with ESMTP; 28 Nov 2005 00:24:17 -0500 X-IronPort-AV: i="3.97,383,1125892800"; d="scan'208"; a="1661382526:sNHT17531728" From: Mike Eubanks To: freebsd-stable@freebsd.org In-Reply-To: <20051127204344.GB3175@xor.obsecurity.org> References: <1132964757.831.20.camel@yak.mseubanks.net> <43891EA5.2020206@mac.com> <1133083658.838.109.camel@yak.mseubanks.net> <20051127204344.GB3175@xor.obsecurity.org> Content-Type: text/plain Date: Sun, 27 Nov 2005 21:24:15 -0800 Message-Id: <1133155455.868.135.camel@yak.mseubanks.net> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: NFS network load on 5.4-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mse_software@charter.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2005 05:24:37 -0000 On Sun, 2005-11-27 at 15:43 -0500, Kris Kennaway wrote: > On Sun, Nov 27, 2005 at 01:27:38AM -0800, Mike Eubanks wrote: > > On Sat, 2005-11-26 at 21:49 -0500, Chuck Swiger wrote: > > > Mike Eubanks wrote: > > > > As soon as I mount my NFS file systems, the network load > > > > increases to a constant 80%-90% of network bandwidth, even > > > > when the file systems are not in use. NFS stats on the client > > > > machine (nfsstat -c) produce the following: > > > > > > > [ ... ] > > > > Fsstat and Requests are increasing very rapidly. Both the client and > > > > server are i386 5.4-STABLE machines. Is this behaviour normal? > > > > > > Sort of. Some fancy parts of X like file-manager/exporer > > > applications tend to call fstat() a lot, but it's probably > > > tunable, and if you enable NFS attribute caching that will > > > help a lot. > > > > Thank you for the reply Chuck. It seems that it is something to do > > with Gnome. I haven't done an upgrade to 2.12 yet, but the difference > > did happen when I refreshed my user configuration to remove any stale > > config files. Using the "top -mio" command I get the following: > > > > [ ... ] > > > > That doesn't look like it is showing a problem to me. In particular > it is indicating 0 I/O. > > > +---- file-manager/explorer? > > | > > client.220312819 > server.nfs: 96 fsstat [|nfs] > > server.nfs > client.220312819: reply ok 168 fsstat POST: DIR 755 ids > > 1001/0 [|nfs] > > > > If this is enough evidence for the file-manager/explore, > > It's evidence that something is peforming NFS I/O, but it doesn't show > what. Perhaps you needed to also use the top -S flag, or to sort the > output by typing 'ototal'. > > > I'll just have > > to accept it for now. I can't find anything about tuning them. As far > > as attribute caching, do you mean the `-o ac*' options to mount_nfs? I > > also noticed two sysctl values, although, I left them unmodified. > > > > vfs.nfs.access_cache_timeout: 2 > > vfs.nfs4.access_cache_timeout: 60 > > Increase the former (you're not using nfs4). Try 60 seconds, for > example. The downside is that you'll have to wait up to a minute for > access changes on the server to be visible to the client, but that's > usually not a big deal unless you're accessing a lot of dynamically > created and destroyed files. > I made the sysctl modification. Still no luck though. The only process that had any activity using the top with the -S option, or after sorting by total, was the swapper/syncer. Even then, it was hardly active. The network traffic persists. -- Mike Eubanks