X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 760958B9CA9 for ; Wed, 2 Feb 2005 18:19:37 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 31231-05 for ; Wed, 2 Feb 2005 18:19:35 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by svr1.postgresql.org (Postfix) with ESMTP id BA6958B9C21 for ; Wed, 2 Feb 2005 18:19:34 +0000 (GMT) Received: from [192.168.0.100] (c-24-5-74-176.client.comcast.net[24.5.74.176]) by comcast.net (rwcrmhc13) with ESMTP id <20050202181930015009l1hqe>; Wed, 2 Feb 2005 18:19:31 +0000 Message-ID: <4201195B.6000203@talisys.com> Date: Wed, 02 Feb 2005 10:18:03 -0800 From: William Yu User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruce Momjian Cc: pgsql-performance@postgresql.org Subject: Re: High end server and storage for a PostgreSQL OLTP system References: <200502021737.j12HbAW26543@candle.pha.pa.us> In-Reply-To: <200502021737.j12HbAW26543@candle.pha.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200502/34 X-Sequence-Number: 10363 >>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? Unfortunately, there's no easy way for Intel to have implemented a 64-bit IOMMU under their current restrictions. The memory controller resides on the chipset and to upgrade the functionality significantly, it would probably require changing the bus protocol. It's not that they couldn't do it -- it would just require all Intel chipset/MB vendors/partners to go through the process of creating & validating totally new products. A way lengthier process than just producing 64-bit CPUs that drop into current motherboards.