X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A1AA53A1AD5 for ; Sun, 16 Jan 2005 17:46:03 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 56443-02 for ; Sun, 16 Jan 2005 17:45:56 +0000 (GMT) Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by svr1.postgresql.org (Postfix) with ESMTP id C8BB03A1A9E for ; Sun, 16 Jan 2005 17:45:56 +0000 (GMT) X-EthosMedia-Virus-Scanned: no infections found Received: from [63.195.55.98] (account josh@agliodbs.com HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6914170; Sun, 16 Jan 2005 09:47:35 -0800 From: Josh Berkus Organization: Aglio Database Solutions To: pgsql-performance@postgresql.org Subject: Re: Increasing RAM for more than 4 Gb. using postgresql Date: Sun, 16 Jan 2005 09:44:47 -0800 User-Agent: KMail/1.6.2 Cc: William Yu References: <1105501768.41e49e484d779@webmail.moph.go.th> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501160944.47511.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/200 X-Sequence-Number: 9890 William, > The theshold for using PAE is actually far lower than 4GB. 4GB is the > total memory address space -- split that in half for 2GB for userspace, > 2GB for kernel. The OS cache resides in kernel space -- after you take > alway the memory allocation for devices, you're left with a window of > roughly 900MB. I'm curious, how do you get 1.1GB for memory allocation for devices? -- Josh Berkus Aglio Database Solutions San Francisco