pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Increasing RAM for more than 4 Gb. using postgresql
23+ messages / 11 participants
[nested] [flat]

* Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-12 03:49  amrit@health2.moph.go.th
  0 siblings, 3 replies; 23+ messages in thread

From: amrit@health2.moph.go.th @ 2005-01-12 03:49 UTC (permalink / raw)
  To: pgsql-performance

I wonder  if I would like to increase more RAM from 4 Gb. to 6 Gb. [which I hope
to increase more performance ] and I now I used RH 9 and Pgsql 7.3.2 ON DUAL
Xeon 3.0 server thay has the limtation of 4 Gb. ram, I should use which OS
between FC 2-3 or redhat EL 3 [which was claimed to support 64 Gb.ram] .May I
use FC 2 [which is freely downloaded] with 6 Gb. and PGsql 7.4 ?
Amrit
Thailand



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-12 11:02  Martin Tedjawardhana <bitboxx@gmail.com>
  parent: amrit@health2.moph.go.th
  2 siblings, 0 replies; 23+ messages in thread

From: Martin Tedjawardhana @ 2005-01-12 11:02 UTC (permalink / raw)
  To: amrit@health2.moph.go.th <amrit@health2.moph.go.th>; +Cc: pgsql-performance

Is that 4GB limit a hardware limitation? If it is, then there is not
much you can do except upgrading the server. If the server is capable
of handling more than 4GB of ram then you can just upgrade the kernel
and enable high memory support (up to 64GB of memory in kernel 2.6.9).
There is no need to migrate your distro, but if you do I recommend
upgrading your Pgsql too.

Martin

On Wed, 12 Jan 2005 10:49:28 +0700, amrit@health2.moph.go.th
<amrit@health2.moph.go.th> wrote:
> I wonder  if I would like to increase more RAM from 4 Gb. to 6 Gb. [which I hope
> to increase more performance ] and I now I used RH 9 and Pgsql 7.3.2 ON DUAL
> Xeon 3.0 server thay has the limtation of 4 Gb. ram, I should use which OS
> between FC 2-3 or redhat EL 3 [which was claimed to support 64 Gb.ram] .May I
> use FC 2 [which is freely downloaded] with 6 Gb. and PGsql 7.4 ?
> Amrit
> Thailand
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly
>



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-12 12:40  Gavin Sherry <swm@linuxworld.com.au>
  parent: amrit@health2.moph.go.th
  2 siblings, 0 replies; 23+ messages in thread

From: Gavin Sherry @ 2005-01-12 12:40 UTC (permalink / raw)
  To: amrit@health2.moph.go.th; +Cc: pgsql-performance

On Wed, 12 Jan 2005 amrit@health2.moph.go.th wrote:

> I wonder  if I would like to increase more RAM from 4 Gb. to 6 Gb. [which I hope
> to increase more performance ] and I now I used RH 9 and Pgsql 7.3.2 ON DUAL
> Xeon 3.0 server thay has the limtation of 4 Gb. ram, I should use which OS
> between FC 2-3 or redhat EL 3 [which was claimed to support 64 Gb.ram] .May I
> use FC 2 [which is freely downloaded] with 6 Gb. and PGsql 7.4 ?
> Amrit
> Thailand

Try 7.4 before the memory upgrade. If you still have performance issues,
try optimising your queries. As I mentioned before, you can join the
#postgresql channel on irc.freenode.net and we can assist.

Gavin




^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-12 12:44  Gavin Sherry <swm@alcove.com.au>
  parent: amrit@health2.moph.go.th
  2 siblings, 2 replies; 23+ messages in thread

From: Gavin Sherry @ 2005-01-12 12:44 UTC (permalink / raw)
  To: amrit@health2.moph.go.th; +Cc: pgsql-performance

On Wed, 12 Jan 2005 amrit@health2.moph.go.th wrote:

> I wonder  if I would like to increase more RAM from 4 Gb. to 6 Gb. [which I hope
> to increase more performance ] and I now I used RH 9 and Pgsql 7.3.2 ON DUAL
> Xeon 3.0 server thay has the limtation of 4 Gb. ram, I should use which OS
> between FC 2-3 or redhat EL 3 [which was claimed to support 64 Gb.ram] .May I
> use FC 2 [which is freely downloaded] with 6 Gb. and PGsql 7.4 ?

There is no problem with free Linux distros handling > 4 GB of memory. The
problem is that 32 hardware must make use of some less than efficient
mechanisms to be able to address the memory.

So, try 7.4 before the memory upgrade. If you still have performance issues,
try optimising your queries. As I mentioned before, you can join the
#postgresql channel on irc.freenode.net and we can assist.

Gavin


> Amrit
> Thailand

Gavin



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-12 14:48  amrit@health2.moph.go.th
  parent: Gavin Sherry <swm@alcove.com.au>
  1 sibling, 1 reply; 23+ messages in thread

From: amrit@health2.moph.go.th @ 2005-01-12 14:48 UTC (permalink / raw)
  To: Gavin Sherry <swm@alcove.com.au>; +Cc: pgsql-performance

> There is no problem with free Linux distros handling > 4 GB of memory. The
> problem is that 32 hardware must make use of some less than efficient
> mechanisms to be able to address the memory.
>
> So, try 7.4 before the memory upgrade. If you still have performance issues,
> try optimising your queries. As I mentioned before, you can join the
> #postgresql channel on irc.freenode.net and we can assist.

Yes , of course I must try to upgrade PGsql to 7.4 and may be  OS to FC 2-3 too.
My server products are intel based [mainboard , CPU ,Case , Power supply ,RAID
Network card] dual Xeon 32 bit 3.0 Ghz which I consulted Thai intel supervisor
and they told me that increasing the ram for more than 4 Gb. may be possible
depending on the OS.
I ask the programmer who wrote that huge query and they told me that it was the
query generated by Delphi 6.0 component and not written by themselve.

Amrit
Thailand



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-12 15:19  Martin Tedjawardhana <bitboxx@gmail.com>
  parent: amrit@health2.moph.go.th
  0 siblings, 0 replies; 23+ messages in thread

From: Martin Tedjawardhana @ 2005-01-12 15:19 UTC (permalink / raw)
  To: amrit@health2.moph.go.th <amrit@health2.moph.go.th>; +Cc: Gavin Sherry <swm@alcove.com.au>; pgsql-performance

> Yes , of course I must try to upgrade PGsql to 7.4 and may be  OS to FC 2-3 too.
> My server products are intel based [mainboard , CPU ,Case , Power supply ,RAID
> Network card] dual Xeon 32 bit 3.0 Ghz which I consulted Thai intel supervisor
> and they told me that increasing the ram for more than 4 Gb. may be possible
> depending on the OS.

I never tried FC before, but I recommend using Debian (with custom
kernel) or if you have the patience: Gentoo. Those are "strictly
business" distros, no unnecesary stuffs running  after installation.
Providing a good base for you to focus on performance tweaks. Others
may have different opinions, though...



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-13 16:32  William Yu <wyu@talisys.com>
  parent: Gavin Sherry <swm@alcove.com.au>
  1 sibling, 2 replies; 23+ messages in thread

From: William Yu @ 2005-01-13 16:32 UTC (permalink / raw)
  To: pgsql-performance

Gavin Sherry wrote:
> There is no problem with free Linux distros handling > 4 GB of memory. The
> problem is that 32 hardware must make use of some less than efficient
> mechanisms to be able to address the memory.

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.

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.



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-16 01:02  amrit@health2.moph.go.th
  parent: William Yu <wyu@talisys.com>
  1 sibling, 1 reply; 23+ messages in thread

From: amrit@health2.moph.go.th @ 2005-01-16 01:02 UTC (permalink / raw)
  To: William Yu <wyu@talisys.com>; +Cc: pgsql-performance


> 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 =
[root@data3 /]# cat < /proc/sys/kernel/shmmax
4000000000
shmall =
[root@data3 /]# 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



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-16 17:44  Josh Berkus <josh@agliodbs.com>
  parent: William Yu <wyu@talisys.com>
  1 sibling, 1 reply; 23+ messages in thread

From: Josh Berkus @ 2005-01-16 17:44 UTC (permalink / raw)
  To: pgsql-performance; +Cc: William Yu <wyu@talisys.com>

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



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-17 17:43  William Yu <wyu@talisys.com>
  parent: Josh Berkus <josh@agliodbs.com>
  0 siblings, 1 reply; 23+ messages in thread

From: William Yu @ 2005-01-17 17:43 UTC (permalink / raw)
  To: pgsql-performance

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?
> 



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-17 17:43  William Yu <wyu@talisys.com>
  parent: amrit@health2.moph.go.th
  0 siblings, 1 reply; 23+ messages in thread

From: William Yu @ 2005-01-17 17:43 UTC (permalink / raw)
  To: pgsql-performance

amrit@health2.moph.go.th wrote:
>>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?

Upgrade to 64-bit processors + 64-bit linux.



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-17 23:17  amrit@health2.moph.go.th
  parent: William Yu <wyu@talisys.com>
  0 siblings, 2 replies; 23+ messages in thread

From: amrit@health2.moph.go.th @ 2005-01-17 23:17 UTC (permalink / raw)
  To: William Yu <wyu@talisys.com>; +Cc: pgsql-performance

> >>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 change this hitting?
>
> Upgrade to 64-bit processors + 64-bit linux.

Does the PAE help linux in handling the memory of more than 4 Gb limit in 32 bit
archetech ? My intel server board could handle the mem of 12 Gb [according to
intel spec.] and if I use Fedora C2 with PAE , will it useless for mem of more
than >4Gb.?

Any comment please?
Amrit
Thailand




^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-17 23:36  Dave Cramer <pg@fastcrypt.com>
  parent: amrit@health2.moph.go.th
  1 sibling, 1 reply; 23+ messages in thread

From: Dave Cramer @ 2005-01-17 23:36 UTC (permalink / raw)
  To: amrit@health2.moph.go.th; +Cc: William Yu <wyu@talisys.com>; pgsql-performance

Amrit,

It's not useless, it's just not optimal.

All operating systems, FC2, FC3, .... will have the same problem with
greater than 4G of memory on a 32 bit processor.

The *only* way to avoid this is to go to a 64 bit processor (opteron) 
and then
for greater performance use a linux distribution compiled for a 64bit 
processor.

Have you identified and optimized the queries, are you sure you need 
more memory?

Dave

amrit@health2.moph.go.th wrote:

>>>>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 change this hitting?
>>>      
>>>
>>Upgrade to 64-bit processors + 64-bit linux.
>>    
>>
>
>Does the PAE help linux in handling the memory of more than 4 Gb limit in 32 bit
>archetech ? My intel server board could handle the mem of 12 Gb [according to
>intel spec.] and if I use Fedora C2 with PAE , will it useless for mem of more
>than >4Gb.?
>
>Any comment please?
>Amrit
>Thailand
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
>    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>
>  
>

-- 
Dave Cramer
http://www.postgresintl.com
519 939 0336
ICQ#14675561

^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-18 00:16  Mark Kirkwood <markir@coretech.co.nz>
  parent: amrit@health2.moph.go.th
  1 sibling, 1 reply; 23+ messages in thread

From: Mark Kirkwood @ 2005-01-18 00:16 UTC (permalink / raw)
  To: amrit@health2.moph.go.th; +Cc: William Yu <wyu@talisys.com>; pgsql-performance

amrit@health2.moph.go.th wrote:

> 
> Does the PAE help linux in handling the memory of more than 4 Gb limit in 32 bit
> archetech ? My intel server board could handle the mem of 12 Gb [according to
> intel spec.] and if I use Fedora C2 with PAE , will it useless for mem of more
> than >4Gb.?
> 
> Any comment please?
>
I understand that the 2.6.* kernels are much better at large memory
support (with respect to performance issues), so unless you have a
64-bit machine lying around - this is probably worth a try.

You may need to build a new kernel with the various parameters :

CONFIG_NOHIGHMEM
CONFIG_HIGHMEM4G
CONFIG_HIGHMEM64G

set appropriately (or even upgrade to the latest 2.6.10). I would expect
that some research and experimentation will be required to get the best
out of it - (e.g. the 'bounce buffers' issue).

regards

Mark





^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-18 02:35  amrit@health2.moph.go.th
  parent: Mark Kirkwood <markir@coretech.co.nz>
  0 siblings, 3 replies; 23+ messages in thread

From: amrit@health2.moph.go.th @ 2005-01-18 02:35 UTC (permalink / raw)
  To: Mark Kirkwood <markir@coretech.co.nz>; +Cc: pgsql-performance

> I understand that the 2.6.* kernels are much better at large memory
> support (with respect to performance issues), so unless you have a
> 64-bit machine lying around - this is probably worth a try.
>
> You may need to build a new kernel with the various parameters :
>
> CONFIG_NOHIGHMEM
> CONFIG_HIGHMEM4G
> CONFIG_HIGHMEM64G
>
> set appropriately (or even upgrade to the latest 2.6.10). I would expect
> that some research and experimentation will be required to get the best
> out of it - (e.g. the 'bounce buffers' issue).

In the standard rpm FC 2-3 with a newly install server , would it automatically
detect and config it if I use the mechine with > 4 Gb [6Gb.] or should I
manually config it?
Amrit
Thailand



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-18 02:42  Mark Kirkwood <markir@coretech.co.nz>
  parent: amrit@health2.moph.go.th
  2 siblings, 0 replies; 23+ messages in thread

From: Mark Kirkwood @ 2005-01-18 02:42 UTC (permalink / raw)
  To: amrit@health2.moph.go.th; +Cc: pgsql-performance

amrit@health2.moph.go.th wrote:

> 
> In the standard rpm FC 2-3 with a newly install server , would it automatically
> detect and config it if I use the mechine with > 4 Gb [6Gb.] or should I
> manually config it?
> Amrit
> Thailand

Good question. I dont have FC2-3 here to check. I recommend firing off a
question to fedora-list@redhat.com (you need to subscribe first):

http://www.redhat.com/mailman/listinfo/fedora-list

best wishes

Mark




^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-18 03:03  William Yu <wyu@talisys.com>
  parent: amrit@health2.moph.go.th
  2 siblings, 0 replies; 23+ messages in thread

From: William Yu @ 2005-01-18 03:03 UTC (permalink / raw)
  To: pgsql-performance

My experience is RH9 auto detected machines >= 2GB of RAM and installs 
the PAE bigmem kernel by default. I'm pretty sure the FC2/3 installer 
will do the same.



amrit@health2.moph.go.th wrote:
>>I understand that the 2.6.* kernels are much better at large memory
>>support (with respect to performance issues), so unless you have a
>>64-bit machine lying around - this is probably worth a try.
>>
>>You may need to build a new kernel with the various parameters :
>>
>>CONFIG_NOHIGHMEM
>>CONFIG_HIGHMEM4G
>>CONFIG_HIGHMEM64G
>>
>>set appropriately (or even upgrade to the latest 2.6.10). I would expect
>>that some research and experimentation will be required to get the best
>>out of it - (e.g. the 'bounce buffers' issue).
> 
> 
> In the standard rpm FC 2-3 with a newly install server , would it automatically
> detect and config it if I use the mechine with > 4 Gb [6Gb.] or should I
> manually config it?
> Amrit
> Thailand
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly
> 



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-18 10:38  D'Arcy J.M. Cain <darcy@NetBSD.org>
  parent: Dave Cramer <pg@fastcrypt.com>
  0 siblings, 0 replies; 23+ messages in thread

From: D'Arcy J.M. Cain @ 2005-01-18 10:38 UTC (permalink / raw)
  To: pg@fastcrypt.com; +Cc: amrit@health2.moph.go.th; wyu@talisys.com; pgsql-performance

On Mon, 17 Jan 2005 18:36:35 -0500
Dave Cramer <pg@fastcrypt.com> wrote:
> The *only* way to avoid this is to go to a 64 bit processor (opteron) 
> and then
> for greater performance use a linux distribution compiled for a 64bit 
> processor.

Or NetBSD (http://www.NetBSD.org/) which has been 64 bit clean since
1995 and has had the Opteron port integrated in its main tree (not as
patches to or a separate tree) since April 2003.

-- 
D'Arcy J.M. Cain <darcy@NetBSD.org>
http://www.NetBSD.org/



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-18 12:00  Martin Tedjawardhana <bitboxx@gmail.com>
  parent: amrit@health2.moph.go.th
  2 siblings, 0 replies; 23+ messages in thread

From: Martin Tedjawardhana @ 2005-01-18 12:00 UTC (permalink / raw)
  To: pgsql-performance

Why dont you just grab the latest stable kernel from kernel.org,
customize it, compile it and the see what happens?


On Tue, 18 Jan 2005 09:35:12 +0700, amrit@health2.moph.go.th
<amrit@health2.moph.go.th> wrote:
> > I understand that the 2.6.* kernels are much better at large memory
> > support (with respect to performance issues), so unless you have a
> > 64-bit machine lying around - this is probably worth a try.
> >
> > You may need to build a new kernel with the various parameters :
> >
> > CONFIG_NOHIGHMEM
> > CONFIG_HIGHMEM4G
> > CONFIG_HIGHMEM64G
> >
> > set appropriately (or even upgrade to the latest 2.6.10). I would expect
> > that some research and experimentation will be required to get the best
> > out of it - (e.g. the 'bounce buffers' issue).
> 
> In the standard rpm FC 2-3 with a newly install server , would it automatically
> detect and config it if I use the mechine with > 4 Gb [6Gb.] or should I
> manually config it?
> Amrit
> Thailand
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly
>



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-18 13:04  Nicolai Petri (lists) <lists@petri.cc>
  parent: William Yu <wyu@talisys.com>
  0 siblings, 1 reply; 23+ messages in thread

From: Nicolai Petri (lists) @ 2005-01-18 13:04 UTC (permalink / raw)
  To: William Yu <wyu@talisys.com>; pgsql-performance

This must be a linux'ism because to my knowledge FreeBSD does not keep the 
os-cache mapped into the kernel address space unless it have active objects 
associated with the data.

And FreeBSD also have a default split of 3GB userspace and 1GB. kernelspace 
when running with a default configuration. Linux people might want to try 
other os'es to compare the performance.

Best regards,
Nicolai Petri

Ps. Sorry for my lame MS mailer - quoting is not something it knows how to 
do. :)
----- Original Message ----- 
From: "William Yu" <wyu@talisys.com>


>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?
>>





^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-18 14:38  amrit@health2.moph.go.th
  parent: Nicolai Petri (lists) <lists@petri.cc>
  0 siblings, 1 reply; 23+ messages in thread

From: amrit@health2.moph.go.th @ 2005-01-18 14:38 UTC (permalink / raw)
  To: pgsql-performance

I would like to upgrade both OS kernel and PGsql version , so in my opinion the
best way to handle it is to *backup* the data in .tar and use a newly install
2.6 OS linux [ from 2.4.9] with build in PGsql 7.4.6 rpm[ from 7.3.2]  and may
up the ram to 6 GB. and *restore* the data again.
I wonder whether the PAE [physical address ext.] will be put in place and could
I use the RAM for more than 4 Gb.  Does any one have different idea ? Since
upgrade to Operon 64 Bit needs a lot of money , I may postpone it for a couple
while.
Any comment ,please.

Amrit
Thailand



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-19 11:12  Richard Huxton <dev@archonet.com>
  parent: amrit@health2.moph.go.th
  0 siblings, 1 reply; 23+ messages in thread

From: Richard Huxton @ 2005-01-19 11:12 UTC (permalink / raw)
  To: amrit@health2.moph.go.th; +Cc: pgsql-performance

amrit@health2.moph.go.th wrote:
> I would like to upgrade both OS kernel and PGsql version , so in my opinion the
> best way to handle it is to *backup* the data in .tar

Just remember if you're going from 7.3.2 => 7.4.x or 8.0 then you'll 
need to use pg_dump not just tar up the directories. If you do use tar, 
remember to backup *all* the directories.

--
   Richard Huxton
   Archonet Ltd



^ permalink  raw  reply  [nested|flat] 23+ messages in thread

* Re: Increasing RAM for more than 4 Gb. using postgresql
@ 2005-01-19 13:41  Dave Cramer <pg@fastcrypt.com>
  parent: Richard Huxton <dev@archonet.com>
  0 siblings, 0 replies; 23+ messages in thread

From: Dave Cramer @ 2005-01-19 13:41 UTC (permalink / raw)
  To: Richard Huxton <dev@archonet.com>; +Cc: pgsql-performance

You can *not* go from any major release to another major release using 
any kind of file backup. Please use pg_dump.

Additionally there are known issues dumping and restoring from 7.3 -> 
7.4 if you use the default copy command. Use the pg_dump --inserts option.

I would still tar the directory just in case you *have* to fall back to 
7.3 for some reason (Better safe than sorry )

Dave

Richard Huxton wrote:

> amrit@health2.moph.go.th wrote:
>
>> I would like to upgrade both OS kernel and PGsql version , so in my 
>> opinion the
>> best way to handle it is to *backup* the data in .tar
>
>
> Just remember if you're going from 7.3.2 => 7.4.x or 8.0 then you'll 
> need to use pg_dump not just tar up the directories. If you do use 
> tar, remember to backup *all* the directories.
>
> -- 
>   Richard Huxton
>   Archonet Ltd
>
> ---------------------------(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
>
>

-- 
Dave Cramer
http://www.postgresintl.com
519 939 0336
ICQ#14675561




^ permalink  raw  reply  [nested|flat] 23+ messages in thread


end of thread, other threads:[~2005-01-19 13:41 UTC | newest]

Thread overview: 23+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-01-12 03:49 Increasing RAM for more than 4 Gb. using postgresql amrit@health2.moph.go.th
2005-01-12 11:02 ` Martin Tedjawardhana <bitboxx@gmail.com>
2005-01-12 12:40 ` Gavin Sherry <swm@linuxworld.com.au>
2005-01-12 12:44 ` Gavin Sherry <swm@alcove.com.au>
2005-01-12 14:48   ` amrit@health2.moph.go.th
2005-01-12 15:19     ` Martin Tedjawardhana <bitboxx@gmail.com>
2005-01-13 16:32   ` William Yu <wyu@talisys.com>
2005-01-16 01:02     ` amrit@health2.moph.go.th
2005-01-17 17:43       ` William Yu <wyu@talisys.com>
2005-01-17 23:17         ` amrit@health2.moph.go.th
2005-01-17 23:36           ` Dave Cramer <pg@fastcrypt.com>
2005-01-18 10:38             ` D'Arcy J.M. Cain <darcy@NetBSD.org>
2005-01-18 00:16           ` Mark Kirkwood <markir@coretech.co.nz>
2005-01-18 02:35             ` amrit@health2.moph.go.th
2005-01-18 02:42               ` Mark Kirkwood <markir@coretech.co.nz>
2005-01-18 03:03               ` William Yu <wyu@talisys.com>
2005-01-18 12:00               ` Martin Tedjawardhana <bitboxx@gmail.com>
2005-01-16 17:44     ` Josh Berkus <josh@agliodbs.com>
2005-01-17 17:43       ` William Yu <wyu@talisys.com>
2005-01-18 13:04         ` Nicolai Petri (lists) <lists@petri.cc>
2005-01-18 14:38           ` amrit@health2.moph.go.th
2005-01-19 11:12             ` Richard Huxton <dev@archonet.com>
2005-01-19 13:41               ` Dave Cramer <pg@fastcrypt.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox