Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 5A4C56339B2 for ; Mon, 11 Jan 2010 18:44:31 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 69357-04 for ; Mon, 11 Jan 2010 22:44:20 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by mail.postgresql.org (Postfix) with ESMTP id 8BE9563298A for ; Mon, 11 Jan 2010 18:44:20 -0400 (AST) Received: by ewy8 with SMTP id 8so22906383ewy.35 for ; Mon, 11 Jan 2010 14:44:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4KMgKXOoi0NmoS3CKYoIXClods+fGuKhElUrH1HYrRc=; b=r5iZJljrxUY3XkAAJcelhJ8PB2RUaZB0U+8tf4j3Orh839QYDbEfDNdE9bN+XakqMA 19TYVn9k+Mx41duY0gV+IsvCaHTZSluxtZEg0a+QlzZBSkBcAAkRadxHCuwjz8L1U5kl 4wJMTGm0IDe+N4sgyBrrD7BytuxFrNI2XesVc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xR8QHTmsOrgkg5ndmyW/wvQJ27nDtotjZIDuIz8CqZiMrQ67ZP8UxWV1Uv9WMjSxcG D5TDBsDgB1/JBASOEo0fdnYUuupt3C6N4M+0cBloA8wLxWMlUt4QzIxNcMD94Yz78c/Z r5CKkXZ33OAJE0IvfYGCKvE/V+9QdsohRGiG8= MIME-Version: 1.0 Received: by 10.216.89.18 with SMTP id b18mr2151818wef.14.1263249858451; Mon, 11 Jan 2010 14:44:18 -0800 (PST) In-Reply-To: <4B4BA058.4070703@2ndquadrant.com> References: <61039b861001110544o2c352763q13dcf9d78a156714@mail.gmail.com> <61039b861001110842g15bb1f26jc50b6e6762e01427@mail.gmail.com> <61039b861001110949n699f0bd1pf3c878fa4c739891@mail.gmail.com> <4B4BA058.4070703@2ndquadrant.com> Date: Mon, 11 Jan 2010 15:44:18 -0700 Message-ID: Subject: Re: performance config help From: Scott Marlowe To: Greg Smith Cc: Bob Dusek , pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.589 tagged_above=-10 required=5 tests=BAYES_00=-2.599, FH_DATE_PAST_20XX=3.188 X-Spam-Level: X-Archive-Number: 201001/227 X-Sequence-Number: 37107 On Mon, Jan 11, 2010 at 3:04 PM, Greg Smith wrote: > Scott Marlowe wrote: >> >> So, I took a break from writing and searched for some more info on the >> 74xx series CPUs, and from reading lots of articles, including this >> one: >> http://www.anandtech.com/cpuchipsets/intel/showdoc.aspx?i=3D3414 >> It seems apparent that the 74xx series if a great CPU, as long as >> you're not memory bound. >> > > This is why I regularly end up recommending people consider Intel's desig= ns > here so often, the ones that use triple-channel DDR3, instead of any of t= he > AMD ones. =A0It's extremely easy to end up with a memory-bound workload > nowadays, at which point all the CPU power in the world doesn't help you > anymore. The DDR3 Nehalem and DDR2 AMD are both actually pretty close in real world use on 4 or more socket machines. Most benchmarks on memory bandwidth give no huge advantage to either one or the other. They both max out at about 25GB/s. It's the older Xeon base 74xx chipsets without integrated memory controllers that seem to have such horrible bandwidth because they're not multi-channel. For dual socket the Nehalem is pretty much the king. By the time you get to 8 sockets AMD is still ahead. Just avoid anything older than nehalem or istanbul.