From owner-freebsd-questions Wed Mar 4 00:27:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24378 for freebsd-questions-outgoing; Wed, 4 Mar 1998 00:27:11 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24372 for ; Wed, 4 Mar 1998 00:27:06 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id DAA00336; Wed, 4 Mar 1998 03:26:54 -0500 (EST) (envelope-from toor) Message-Id: <199803040826.DAA00336@dyson.iquest.net> Subject: Re: page faults etc. In-Reply-To: from Doug White at "Mar 3, 98 08:09:04 pm" To: dwhite@resnet.uoregon.edu Date: Wed, 4 Mar 1998 03:26:54 -0500 (EST) Cc: mike@chaski.com, questions@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White said: > On Tue, 3 Mar 1998, michael dorin wrote: > > > > > How do I tell how many page faults my system is having? > > systat -vmstat , Trp item (this is total system traps, but includes > page faults). > Page faults are generally not useful info. That info is more useful to me to make sure that I have minimized them. There are sort-of three levels of faults, one that requires I/O to complete, one that requires copying or zeroing a page, and one that simply maps a page into memory. These are listed in descending time to process, and the times span several orders of magnitude or more. > > > What do I look for as bad? > > What do I look for as good? > > You really want to be concerned about swap usage, this is probably an > easier-to-track barometer. If your swap system is very active (lots of > in/out) you probably need more RAM. > > Mr. Dyson? > Yes, the paging I/O is the most important parameter, and too much I/O will impact performance severely. FreeBSD tries to minimize the amount of paging I/O by careful page mgmt, but excessive paging will clobber performance on any system. One more note though, if you have excess RAM, the system will likely use it as a very effective disk cache. There is a point of diminishing returns. With my workstation workload, it seems that I am at that point between 64MB and 128MB. Performance is still reasonable at 32MB with my workload. When running on 16-32MB, the system starts feeling like WinNT with 64MB. I normally run with 200+ MB, but with memory so cheap, why not? :-). -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message