From owner-freebsd-stable Mon Dec 1 13:05:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA17733 for stable-outgoing; Mon, 1 Dec 1997 13:05:19 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from bullfrog.winternet.com (jstepka@bullfrog.winternet.com [204.246.64.212]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA17718 for ; Mon, 1 Dec 1997 13:05:07 -0800 (PST) (envelope-from jstepka@bullfrog.winternet.com) Received: from localhost (jstepka@localhost) by bullfrog.winternet.com (8.8.5/8.8.5) with SMTP id OAA18636; Mon, 1 Dec 1997 14:59:44 -0600 (CST) Date: Mon, 1 Dec 1997 14:59:35 -0600 (CST) From: Justen Stepka To: Tom cc: Mattias Pantzare , Justen Stepka , FreeBSD-stable@freebsd.org Subject: Re: CPU Load In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 30 Nov 1997, Tom wrote: > > On Mon, 1 Dec 1997, Mattias Pantzare wrote: > > > On Sat, 29 Nov 1997, Justen Stepka wrote: > > > > > Recently I added memory to my NFS server (dx4-100 now w/ 32 megs of RAM), > > > when I did this the overall system preformance increased dramiticly. The > > > problem that I noticed was that when using NFS/NIS the CPU load climbs to > > > about 4.0+, is there a special reason that this might be happening? > > > > The load value is not CPU load. It is the average number of processes > > ready to run or waiting for disk I/O to complete. > > No, it is the average number of processes that are ready-to-run. > Processes waiting for disk io (or any io) are not ready to run. > > > So it is normal for a NFS server to have a high load, as it is often > > waiting for disk I/O. > > It is normal for NFS servers to have a low load, because NFS serving is > not CPU intensive, and io bound. > > A load of 4+ for a NFS server is not normal. I would suggest > determining which processes are using CPU time. the processes that are taking so much CPU time are the nsfd daemons, there are two of them with a 35%+ WCPU and CPU. Justen Stepka