Re: [PERFORM] Increasing RAM for more than 4 Gb. using postgresql
> 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 set shammax = [EMAIL PROTECTED] /]# cat < /proc/sys/kernel/shmmax 40 shmall = [EMAIL PROTECTED] /]# cat < /proc/sys/kernel/shmall 134217728 Is that ok for 4 Gb. mechine? > Since the optimal state is to allocate a small amount of memory to > Postgres and leave a huge chunk to the OS cache, this means you are > already hitting the PAE penalty at 1.5GB of memory. > How could I chang this hitting? Thanks Amrit Thailand ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [PERFORM] Increasing RAM for more than 4 Gb. using postgresql
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 ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
