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 0BFFD3A3D80 for ; Mon, 17 Jan 2005 17:43:33 +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 31464-03 for ; Mon, 17 Jan 2005 17:43:19 +0000 (GMT) Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.250.190.2]) by svr1.postgresql.org (Postfix) with ESMTP id AA6D23A3DD3 for ; Mon, 17 Jan 2005 17:43:16 +0000 (GMT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 51253313CD; Mon, 17 Jan 2005 18:43:14 +0100 (MET) From: William Yu X-Newsgroups: pgsql.performance Subject: Re: Increasing RAM for more than 4 Gb. using postgresql Date: Mon, 17 Jan 2005 09:43:10 -0800 Organization: Hub.Org Networking Services Lines: 21 Message-ID: References: <1105501768.41e49e484d779@webmail.moph.go.th> <200501160944.47511.josh@agliodbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en In-Reply-To: <200501160944.47511.josh@agliodbs.com> To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200501/205 X-Sequence-Number: 9895 I inferred this from reading up on the compressed vm project. It can be higher or lower depending on what devices you have in your system -- however, I've read messages from kernel hackers saying Linux is very aggressive in reserving memory space for devices because it must be allocated at boottime. Josh Berkus wrote: > 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? >