X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.225.181]) by svr1.postgresql.org (Postfix) with ESMTP id CA979D1C4C8 for ; Tue, 22 Jul 2003 17:54:38 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr5.postgresql.org [64.117.225.181]) (amavisd-new, port 10024) with ESMTP id 96653-03 for ; Tue, 22 Jul 2003 17:54:27 +0000 (GMT) Received: from indygecko.com (h24-77-222-182.ok.shawcable.net [24.77.222.182]) by svr1.postgresql.org (Postfix) with ESMTP id 53604D1C4BF for ; Tue, 22 Jul 2003 14:54:27 -0300 (ADT) Received: from [192.168.10.10] ([::ffff:192.168.10.10]) by indygecko.com with esmtp; Tue, 22 Jul 2003 10:54:25 -0700 Subject: Re: Dual Xeon + HW RAID question From: Jord Tanner To: Bruce Momjian Cc: "SZUCS =?ISO-8859-1?Q?G=E1bor?=" , pgsql-performance@postgresql.org In-Reply-To: <200307221739.h6MHdGd03573@candle.pha.pa.us> References: <200307221739.h6MHdGd03573@candle.pha.pa.us> Organization: Message-Id: <1058896464.4339.46.camel@gecko> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 22 Jul 2003 10:54:24 -0700 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/371 X-Sequence-Number: 2664 On Tue, 2003-07-22 at 10:39, Bruce Momjian wrote: > But CPU affinity isn't realated to hyperthreading, as far as I know. > CPU affinity tries to keep processes on the same cpu in case there is > still valuable info in the cpu cache. > It is true that CPU affinity is designed to prevent the dump of valuable CPU cache. My thought is that if you are trying to prevent CPU contention, you could use CPU affinity to prevent 2 postmaster processes from running simultaneously on the same die. Am I out to lunch here? I've not worked with CPU affinity before, so I'm not familiar with the intimate details. -- Jord Tanner