Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 6B2559FC169 for ; Fri, 23 Feb 2007 18:23:15 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 71925-01 for ; Fri, 23 Feb 2007 18:23:07 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.230]) by postgresql.org (Postfix) with ESMTP id 3FD989FC204 for ; Fri, 23 Feb 2007 18:23:11 -0400 (AST) Received: by wx-out-0506.google.com with SMTP id i28so657992wxd for ; Fri, 23 Feb 2007 14:23:10 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aWic3wZ0D2nqCCmwreFPmnHzKvbQu3B6ZBIAv7I2oNSZPTe3Q2Lu/VnimZRXavYqXJdOYYnTkIKwMEEM3gbINL6RP5+3DqUxqq9Vls0tp+eVBZxr5SQaRfhtXTt1SI3s7Oy9H//pu2U04O3OQQJh9qXozbD3P+92pep2g3LX3A0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gr2k9acVFU88+w0EhfuGWWzkAYRsYTDUPn4PVsZiWY8WP4eJWbeWF6yJQuX/iFWWeMP78N3Iv39AjgwlzNVwjie6bx+xMsUuoYizM+g2jpGWYHVwFVccBvEEDM7ESNxG2SNqhc/qN5AS7AlOjKaW0o8F1G29NH1B8QmuiJGqNFI= Received: by 10.90.113.18 with SMTP id l18mr2750395agc.1172269390334; Fri, 23 Feb 2007 14:23:10 -0800 (PST) Received: by 10.90.113.7 with HTTP; Fri, 23 Feb 2007 14:23:10 -0800 (PST) Message-ID: <1d4e0c10702231423k55ab792ewd9a33efb77ded1b1@mail.gmail.com> Date: Fri, 23 Feb 2007 23:23:10 +0100 From: "Guillaume Smet" To: "Joshua D. Drake" Subject: Re: which Xeon processors don't have the context switching problem Cc: josh@agliodbs.com, pgsql-performance@postgresql.org, Geoffrey In-Reply-To: <45DF5DA9.90002@commandprompt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45DF3B15.1070609@3times25.net> <200702231330.57014.josh@agliodbs.com> <45DF5DA9.90002@commandprompt.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/264 X-Sequence-Number: 23318 On 2/23/07, Joshua D. Drake wrote: > Also isn't it pretty much *not* a problem with current versions of > PostgreSQL? We had a really *big* scalability problem with a quad Xeon MP 2.2 and PostgreSQL 7.4. The problem is mostly gone since we upgraded to 8.1 a year ago. Woodcrest seems to perform really well with PostgreSQL according to what I can read on the Internet so we will probably change the server for a dual Woodcrest in a few months. -- Guillaume