postgresql +AMD64 +big address spaces - does it work?

From: "Andy B" <abhousehuntRE-M--O--V-E(at)blueyonder(dot)co(dot)uk>
To: pgsql-general(at)postgresql(dot)org
Subject: postgresql +AMD64 +big address spaces - does it work?
Date: 2004-07-01 12:41:00
Message-ID: wDTEc.525$HQ1.399@fe2.news.blueyonder.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

If I bought one of these boxes/OS combos as a postgresql database server,
would postgresql be able to make the best use of it with a huge (e.g. 40GB)
database?

Box: HP ProLiant DL585, with 4 AMD64 CPUs and 64GB of RAM. (other
vendor options also exist)
OS: SUSE enterprise 8 linux for AMD

(links to product info at bottom)

e.g. Could postgresql make use of most of this address space to map a huge
database (say 40GB) all paged into RAM at once?

----
According to Suse, a process running on such a setup can individually
address 0.5 terabytes of address space, and at any one point, with the
hardware above, up to 64GB (minus a bit!) of this address space could be
paged into physical memory at any one time.
----

According to the docs I could find, I just need to do the following:

1. set postgresql.conf->shared_buffers to a value like (40GB/8KB),

2. Check cat /proc/sys/kernel/shmmax is big enough, or successfully increase
it to > 40GB

From experience that's a long way from knowing it will work. Does anyone
have any experience at all with such big memory configurations?

Many thanks,
Andy

______
My references:
Suse: www.suse.com/amd64 and
www.suse.com/en/business/products/server/sles/sles8_amd64.pdf
HP: http://h18004.www1.hp.com/products/servers/proliantdl585/index.html

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2004-07-01 12:48:36 Re: Bug in function to_char() !!
Previous Message Doug McNaught 2004-07-01 12:23:18 Re: Problems restarting after database crashed (signal