From owner-freebsd-performance@FreeBSD.ORG Tue Jul 22 12:19:41 2003 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDEC037B401; Tue, 22 Jul 2003 12:19:41 -0700 (PDT) Received: from svaha.com (svaha.com [64.46.156.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5F6143F3F; Tue, 22 Jul 2003 12:19:40 -0700 (PDT) (envelope-from meconlen@obfuscated.net) Received: from obfuscated.net (internal.neutelligent.com [64.156.25.4]) (AUTH: LOGIN meconlen, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by svaha.com with esmtp; Tue, 22 Jul 2003 15:19:38 -0400 Message-ID: <3F1D8E45.7090101@obfuscated.net> Date: Tue, 22 Jul 2003 15:19:33 -0400 From: Michael Conlen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sean Chittenden References: <200307191818.13516.paul@pathiakis.com> <20030720110939.GN24507@perrin.int.nxad.com> <20030720164237.GC55392@nasby.net> <20030720205339.GP24507@perrin.int.nxad.com> <20030722143449.B10666@smtp.k12us.com> <20030722185527.GU64860@perrin.int.nxad.com> In-Reply-To: <20030722185527.GU64860@perrin.int.nxad.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-database@freebsd.org cc: freebsd-performance@freebsd.org cc: Christopher Weimann cc: Paul Pathiakis Subject: Re: Tuning for PostGreSQL Database X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 19:19:42 -0000 Sean Chittenden wrote: >>>You might want to get in the habit of using sysctl for getting >>>that kind of info. `sysctl -d vfs.bufspace` >>> >>> >>I'm confused. Everything I have ever read about FreeBSD indicates >>that it uses all free ram for the disk cache. >> >> > >>From loader(8): > > kern.maxbcache > Limits the amount of KVM reserved for use by the buffer > cache, specified in bytes. The default maximum is 200MB. > This parameter is used to prevent the buffer cache from > eating too much KVM in large-memory machine configurations. > Only mess around with this parameter if you need to greatly > extend the KVM reservation for other resources such as the > swap zone or NMBCLUSTERS. Note that the NBUF parameter > will override this limit. Modifies VM_BCACHE_SIZE_MAX. > >-sc > > Aren't we talking about two different things here, the buffer cache and the inactive pages? -- Michael Conlen