From owner-freebsd-stable Sat Mar 21 08:58:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28064 for freebsd-stable-outgoing; Sat, 21 Mar 1998 08:58:31 -0800 (PST) (envelope-from owner-freebsd-stable@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 IAA28057 for ; Sat, 21 Mar 1998 08:58:27 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA04264; Sat, 21 Mar 1998 11:58:28 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803211658.LAA04264@dyson.iquest.net> Subject: Re: No disk cache after memory upgrade (2.2/pii-300/512mb) In-Reply-To: <199803210119.WAA21371@gaia.coppe.ufrj.br> from Joao Carlos Mendes Luis at "Mar 20, 98 10:19:14 pm" To: jonny@coppe.ufrj.br (Joao Carlos Mendes Luis) Date: Sat, 21 Mar 1998 11:58:28 -0500 (EST) Cc: robh@imdb.com, stable@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-stable@FreeBSD.ORG Precedence: bulk > #define quoting(Rob Hartill) > // > Yep... I get the same thing... one of our machines just sits there, always > // > with free memory. It's never doing anything (it's rare to see any load at > // > all) - the same with the others - but their cache fills up and they never > // > have free memory. > // > > // > Bizare eh? > // > // Strangely, after about 24 hours of being cache-less, it suddenly came > // to life again. I'm wondering if it's just not reporting the cache for > // some unknown reason. > > Pay attention to the Active Memory size, and see if it grows with > disk access. Disk cache can also be listed as Active Memory. > I don't know exactly why, but this is most commom if your partitions > are mounted async. > That is true. Note that all of your memory is used as a disk cache, if it isn't used as program memory. The memory usage is less than your total available memory only when the system is just started, or a program has exited (or freed memory), a disk file has been deleted, or a filesystem is dismounted. It is hard to tell if you need more memory, but maybe the best measure is excessive swap pager activity. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message