X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 73B73D1C4C1 for ; Tue, 22 Jul 2003 19:18:55 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 85772-06 for ; Tue, 22 Jul 2003 16:18:10 -0300 (ADT) Received: from indygecko.com (h24-77-222-182.ok.shawcable.net [24.77.222.182]) by svr1.postgresql.org (Postfix) with ESMTP id 19D5DD1C4B7 for ; Tue, 22 Jul 2003 16:18:53 -0300 (ADT) Received: from [192.168.10.10] ([::ffff:192.168.10.10]) by indygecko.com with esmtp; Tue, 22 Jul 2003 12:18:52 -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: <200307221850.h6MIocK10571@candle.pha.pa.us> References: <200307221850.h6MIocK10571@candle.pha.pa.us> Organization: Message-Id: <1058901531.4339.57.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 12:18:52 -0700 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/377 X-Sequence-Number: 2670 On Tue, 2003-07-22 at 11:50, Bruce Momjian wrote: > Jord Tanner wrote: > > 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. > > I guess you could but it is the backends that use the cpu. I don't > think manually specifying affinity will work for most applications. This is beating a dead horse, but I'll take one more kick at it. CPU affinity is defined by a bit mask, so multiple processors can be selected. It is also inherited by child processes, so assigning CPU 0 and CPU 2 (which I assume would be on different dies in a dual processor hyper-threading system) to the parent postmaster should prevent CPU contention with respect to the postgres backend. I would be very interested to see if any advantage could be gained by a combination of multiple HT processors and cpu affinity over multiple non-HT processors. Yet Another Performance Testing To Do (YAPTTD)! -- Jord Tanner