pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jord Tanner <jord@indygecko.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: SZUCS Gábor <surrano@mailbox.hu>
Cc: pgsql-performance@postgresql.org
Subject: Re: Dual Xeon + HW RAID question
Date: 22 Jul 2003 12:18:52 -0700
Message-ID: <1058901531.4339.57.camel@gecko> (raw)
In-Reply-To: <200307221850.h6MIocK10571@candle.pha.pa.us>
References: <200307221850.h6MIocK10571@candle.pha.pa.us>

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 <jord@indygecko.com>




view thread (16+ messages)

Message-ID: <1058901531.4339.57.camel@gecko>
Permalink:  ../1058901531.4339.57.camel@gecko/
Also on:    postgresql.org/message-id/1058901531.4339.57.camel@gecko

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: jord@indygecko.com, pgman@candle.pha.pa.us, surrano@mailbox.hu
  Subject: Re: Dual Xeon + HW RAID question
  In-Reply-To: <1058901531.4339.57.camel@gecko>
  References: <200307221850.h6MIocK10571@candle.pha.pa.us> <1058901531.4339.57.camel@gecko>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox