From owner-freebsd-questions@FreeBSD.ORG Fri Sep 12 09:59:08 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 32B2D16A4BF for ; Fri, 12 Sep 2003 09:59:08 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EAD143FF7 for ; Fri, 12 Sep 2003 09:59:07 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37]) by comcast.net (rwcrmhc13) with ESMTP id <20030912165903015003d5m5e>; Fri, 12 Sep 2003 16:59:04 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37] (may be forged)) by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h8CGwxCo065930; Fri, 12 Sep 2003 12:58:59 -0400 (EDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h8CGwwZS065927; Fri, 12 Sep 2003 12:58:58 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: jesse@wingnet.net References: <20030911231742.GA61528@dan.emsphone.com> From: Lowell Gilbert Date: 12 Sep 2003 12:58:58 -0400 In-Reply-To: Message-ID: <44znharlil.fsf@be-well.ilk.org> Lines: 38 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: `top` process memory usage: SIZE vs RES X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2003 16:59:08 -0000 Jesse Guardiani writes: > 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. :) No, probably not. The OS disk-caching is probably *more* efficient than letting the data go into a RAM disk at each stage. Considerably so, in fact. > > > >> 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? No, it's not in kernel space. "Core" just refers to RAM: the term is held over from the days when main memory was constructed out of little magnetic cores in a wire matrix. > If so, how is that significant? Why should I care? If your system starts swapping heavily, that will often be the clue that tells you why. Just one example.