pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: William Yu <wyu@talisys.com>
To: pgsql-performance@postgresql.org
Subject: Re: Tuning for mid-size server
Date: Tue, 21 Oct 2003 11:27:08 -0700
Message-ID: <bn3tpt$1mos$1@news.hub.org> (raw)
In-Reply-To: <200310211012.15845.josh@agliodbs.com>
References: <Pine.LNX.4.33.0310211042040.10616-100000@css120.ihs.com>
	<200310211012.15845.josh@agliodbs.com>

> So what is the ceiling on 32-bit processors for RAM? Most of the 64-bit 
> vendors are pushing Athalon64 and G5 as "breaking the 4GB barrier", and even 
> I can do the math on 2^32.   All these 64-bit vendors, then, are talking 
> about the limit on ram *per application* and not per machine?

64-bit CPU on 64-bit OS. Up to physical address limit for anything and 
everything.

64-bit CPU on 32-bit OS. Up to 4GB minus the kernel allocation -- which 
is usually 2GB on Windows and Linux. On Windows, you can up this to 3GB 
by using the /3GB switch. Linux requires a kernel recompile. PAE is then 
used to "move" the memory window to point to different areas of the 
physical memory.




view thread (29+ messages)  latest in thread

Message-ID: <bn3tpt$1mos$1@news.hub.org>
Permalink:  ../bn3tpt$1mos$1@news.hub.org/
Also on:    postgresql.org/message-id/bn3tpt$1mos$1@news.hub.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: wyu@talisys.com
  Subject: Re: Tuning for mid-size server
  In-Reply-To: <bn3tpt$1mos$1@news.hub.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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