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: High end server and storage for a PostgreSQL OLTP system
Date: Tue, 01 Feb 2005 20:25:09 -0800
Message-ID: <ctpkn9$tjp$1@news.hub.org> (raw)
In-Reply-To: <20050201112727.GF32356@decibel.org>
References: <41FE97FC.3060106@streppone.it>
	<20050201045645.GC32356@decibel.org>
	<41FF2337.7070809@streppone.it>
	<20050201112727.GF32356@decibel.org>

Jim C. Nasby wrote:
> On Tue, Feb 01, 2005 at 07:35:35AM +0100, Cosimo Streppone wrote:
> 
>>>You might look at Opteron's, which theoretically have a higher data
>>>bandwidth. If you're doing anything data intensive, like a sort in
>>>memory, this could make a difference.
>>
>>Would Opteron systems need 64-bit postgresql (and os, gcc, ...)
>>build to have that advantage?
> 
>  
> Well, that would give you the most benefit, but the memory bandwidth is
> still greater than on a Xeon. There's really no issue with 64 bit if
> you're using open source software; it all compiles for 64 bits and
> you're good to go. http://stats.distributed.net runs on a dual opteron
> box running FreeBSD and I've had no issues.

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.)



view thread (21+ messages)  latest in thread

Message-ID: <ctpkn9$tjp$1@news.hub.org>
Permalink:  ../ctpkn9$tjp$1@news.hub.org/
Also on:    postgresql.org/message-id/ctpkn9$tjp$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: High end server and storage for a PostgreSQL OLTP system
  In-Reply-To: <ctpkn9$tjp$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