pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: High end server and storage for a PostgreSQL OLTP system
Date: Wed, 02 Feb 2005 22:35:19 -0500
Message-ID: <m3hdkunwnc.fsf@knuth.knuth.cbbrowne.com> (raw)
References: <ctpkn9$tjp$1@news.hub.org>
	<200502021737.j12HbAW26543@candle.pha.pa.us>

pgman@candle.pha.pa.us (Bruce Momjian) wrote:
> William Yu wrote:
>> > 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.)
>
> I thought Intel was copying AMD's 64-bit API.  Is Intel's
> implementation as poor as you description?  Does Intel have any better
> 64-bit offering other than the Itanium/Itanic?



view thread (21+ messages)  latest in thread

Message-ID: <m3hdkunwnc.fsf@knuth.knuth.cbbrowne.com>
Permalink:  ../m3hdkunwnc.fsf@knuth.knuth.cbbrowne.com/
Also on:    postgresql.org/message-id/m3hdkunwnc.fsf@knuth.knuth.cbbrowne.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: cbbrowne@acm.org
  Subject: Re: High end server and storage for a PostgreSQL OLTP system
  In-Reply-To: <m3hdkunwnc.fsf@knuth.knuth.cbbrowne.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