From owner-freebsd-hackers Fri Mar 6 18:58:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09525 for freebsd-hackers-outgoing; Fri, 6 Mar 1998 18:58:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09519 for ; Fri, 6 Mar 1998 18:58:44 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id UAA06647 for ; Fri, 6 Mar 1998 20:58:40 -0600 (CST) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199803070258.UAA06647@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 Reply-to: ccsanady@iastate.edu To: freebsd-hackers@FreeBSD.ORG Subject: VM/Buffer cache sizing... (e.g. for serving NFS) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Mar 1998 20:58:39 -0600 From: Chris Csanady Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had some questions about the workings of the buffer cache in our VM system. Currently, it seems that although the size of the cache varies dynamically, the maximum is still preset at compile time. Is this accurate? The reason I ask, is that in linux, it seems to grow dynamically until it reaches near the limit of your physical memory. I'm not sure how exactly it works, but can something similar be done it FreeBSD? If the limit were to be set really high though, would it starve everything else? When serving NFS to a large set of machines, it would allow for the entire file set to remain in cache (at least in our case, with 512M of ram.) Is this type of thing possible? Thanks, Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message