Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id A0A0F9FC412 for ; Fri, 23 Feb 2007 17:33:45 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 87160-08 for ; Fri, 23 Feb 2007 17:33:39 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 910AE9FC2EF for ; Fri, 23 Feb 2007 17:33:39 -0400 (AST) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l1NLX6x8004028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Feb 2007 13:33:07 -0800 Message-ID: <45DF5DA9.90002@commandprompt.com> Date: Fri, 23 Feb 2007 13:33:29 -0800 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 1.5.0.9 (X11/20070103) MIME-Version: 1.0 To: josh@agliodbs.com CC: pgsql-performance@postgresql.org, Geoffrey Subject: Re: which Xeon processors don't have the context switching problem References: <45DF3B15.1070609@3times25.net> <200702231330.57014.josh@agliodbs.com> In-Reply-To: <200702231330.57014.josh@agliodbs.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Fri, 23 Feb 2007 13:33:08 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/262 X-Sequence-Number: 23316 Josh Berkus wrote: > Geoffrey, > >> I recall a reference on the list indicating that newer Xeon processors >> don't suffer from the context switching problem reported last year. > > Just to be clear, it's a software problem which affects all architectures, > including AMD and Sparc. It's just *worse* on the PIII and P4 generation > Xeons. > Also isn't it pretty much *not* a problem with current versions of PostgreSQL? Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/