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 D7A0B8B9E50 for ; Thu, 3 Feb 2005 03:51:59 +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 69737-03 for ; Thu, 3 Feb 2005 03:51:47 +0000 (GMT) Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.250.190.2]) by svr1.postgresql.org (Postfix) with ESMTP id 462F38B9E68 for ; Thu, 3 Feb 2005 03:51:50 +0000 (GMT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 89CE231DD1; Thu, 3 Feb 2005 04:51:51 +0100 (MET) From: Christopher Browne X-Newsgroups: pgsql.performance Subject: Re: High end server and storage for a PostgreSQL OLTP system Date: Wed, 02 Feb 2005 22:35:19 -0500 Organization: cbbrowne Computing Inc Lines: 40 Message-ID: References: <200502021737.j12HbAW26543@candle.pha.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Corporate Culture, linux) Cancel-Lock: sha1:fCAHGh6JCL0WiKKomUrSInnpLzA= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.073 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/46 X-Sequence-Number: 10375 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?