From owner-freebsd-questions@FreeBSD.ORG Fri Sep 12 07:00:22 2003 Return-Path: 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 B73F216A4BF for ; Fri, 12 Sep 2003 07:00:22 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEAAC44001 for ; Fri, 12 Sep 2003 07:00:21 -0700 (PDT) (envelope-from freebsd-questions@m.gmane.org) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19xoT8-0001A9-00 for ; Fri, 12 Sep 2003 16:00:14 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19xoQx-00018P-00 for ; Fri, 12 Sep 2003 15:57:59 +0200 Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 19xoR3-0008VV-00 for ; Fri, 12 Sep 2003 15:58:05 +0200 From: Jesse Guardiani Date: Fri, 12 Sep 2003 09:58:05 -0400 Organization: WingNET Lines: 36 Message-ID: References: <20030911231742.GA61528@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org User-Agent: KNode/0.7.2 X-Mail-Copies-To: never Sender: news Subject: Re: `top` process memory usage: SIZE vs RES X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2003 14:00:22 -0000 Dan Nelson wrote: > In the last episode (Sep 11), Jesse Guardiani said: >> 1.) Where is my Free memory going? I can't account for it >> in the SIZE and RES columns of the various processes. >> These are relatively constant. > > Disk cache. I thought it might be something like that. My large test messages are being written to disk over and over and over as the message travels down the pipline. Makes a great case for installing a RAM disk. :) > >> 2.) What, exactly, is RES? `man top` describes it as this: >> "RES is the current amount of resident memory", but does >> that mean RES is included in SIZE? Or does that mean that >> RES should be counted in addition to SIZE? > > RES the amount of SIZE that it currently in core OK. To clarify, you mean core kernel memory here? If so, how is that significant? Why should I care? In other words, why would I ever want to know that? Thanks. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net