pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: William Yu <wyu@talisys.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: High end server and storage for a PostgreSQL OLTP system
Date: Wed, 02 Feb 2005 10:49:35 -0800
Message-ID: <420120BF.5050208@talisys.com> (raw)
In-Reply-To: <200502021835.j12IZKA04787@candle.pha.pa.us>
References: <200502021835.j12IZKA04787@candle.pha.pa.us>

Bruce Momjian wrote:
> William Yu wrote:
> 
>>>>You can get 64-bit Xeons also but it takes hit in the I/O department due 
>>>>to the lack of a hardware I/O MMU which limits DMA transfers to 
>>>>addresses below 4GB. This has a two-fold impact:
>>>>
>>>>1) transfering data to >4GB require first a transfer to <4GB and then a 
>>>>copy to the final destination.
>>>>
>>>>2) You must allocate real memory 2X the address space of the devices to 
>>>>act as bounce buffers. This is especially problematic for workstations 
>>>>because if you put a 512MB Nvidia card in your computer for graphics 
>>>>work -- you've just lost 1GB of memory. (I dunno how much the typical 
>>>>SCSI/NIC/etc take up.)
> 
> 
> When you say "allocate real memory 2X" are you saying that if you have
> 16GB of RAM only 8GB is actually usable and the other 8GB is for
> bounce buffers, or is it just address space being used up?
> 

It's 2x the memory space of the devices. E.g. a Nvidia Graphics card w/ 
512MB of RAM would require 1GB of memory to act as bounce buffers. And 
it has to be real chunks of memory in 64-bit mode since DMA transfer 
must drop it into real memory in order to then be copied to > 4GB.



view thread (21+ messages)  latest in thread

Message-ID: <420120BF.5050208@talisys.com>
Permalink:  ../420120BF.5050208@talisys.com/
Also on:    postgresql.org/message-id/420120BF.5050208@talisys.com

 · 

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, pgman@candle.pha.pa.us
  Subject: Re: High end server and storage for a PostgreSQL OLTP system
  In-Reply-To: <420120BF.5050208@talisys.com>

* 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