From owner-freebsd-questions@FreeBSD.ORG Sun Mar 5 23:20:10 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EB8716A420 for ; Sun, 5 Mar 2006 23:20:10 +0000 (GMT) (envelope-from mftuchman@alum.mit.edu) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EFF943D6B for ; Sun, 5 Mar 2006 23:20:08 +0000 (GMT) (envelope-from mftuchman@alum.mit.edu) Received: from [127.0.0.1] (c-68-80-20-253.hsd1.pa.comcast.net[68.80.20.253]) by comcast.net (rwcrmhc12) with ESMTP id <20060305232007m12001eh52e>; Sun, 5 Mar 2006 23:20:07 +0000 Message-ID: <440B7224.4060404@alum.mit.edu> Date: Sun, 05 Mar 2006 18:20:04 -0500 From: Michael Tuchman User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Applications using hard disk too often X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Mar 2006 23:20:10 -0000 I am running freeBSD 5.4 stable on a P133 box with 128 Mb ram. Although I don't think I'm overloading the system, it seems that my system is using virtual memory too often. Admittedly, this is a subjective question where 'too often' means only 'more often than I remember with other *nix-like operating environments on even weaker machines'. Can anybody offer advice on memory management, appropriate places to read in the documentation, or other useful links? I realize that the answer is 'it depends', so what I am asking is really * How can I find out if I change this annoying behavior for the better? * Would upgrading to 6.0 help? This is an experimental box only. There is no critical data on it, so data loss is not an issue when considering options.