From owner-freebsd-database@FreeBSD.ORG Fri Jul 25 23:35:04 2003 Return-Path: Delivered-To: freebsd-database@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A56737B401; Fri, 25 Jul 2003 23:35:04 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5561F43F75; Fri, 25 Jul 2003 23:35:01 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfj2b.dialup.mindspring.com ([165.247.204.75] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19gIdg-0007k3-00; Fri, 25 Jul 2003 23:34:44 -0700 Message-ID: <3F2220C7.F0179FC4@mindspring.com> Date: Fri, 25 Jul 2003 23:33:43 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Weimann References: <20030724173910.GA9364@smtp.k12us.com> <20030725162601.GA35378@smtp.k12us.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4c10426f27d3e889ed0aa6d67ef163ea2667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c cc: freebsd-database@freebsd.org cc: Paul Pathiakis cc: Sean Chittenden cc: freebsd-performance@freebsd.org Subject: Re: Tuning for PostGreSQL Database X-BeenThere: freebsd-database@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Database use and development under FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 06:35:04 -0000 Christopher Weimann wrote: > So I have conflicting documentation. > > I have machine with 4Gig of ram. What is the maximum > value of SHMMAX on FreeBSD? Ideally, you would use memory mapped files for this, and not System V shared memory, so that the OS could implement swapping policies as it saw fit, and could actually swap the data, if nevcessary, instead of it sucking up huge amounts of wired memory. In any case, POSIX deprecated SysV shared memory years ago, and recommends that all code utilize shm_open instead, these days, if you insist on using an interface that sucks up huge amounts of wired pages and KVA space. -- Terry