pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Jord Tanner <jord@indygecko.com>
Cc: SZUCS Gábor <surrano@mailbox.hu>
Cc: pgsql-performance@postgresql.org
Subject: Re: Dual Xeon + HW RAID question
Date: Tue, 22 Jul 2003 13:39:16 -0400 (EDT)
Message-ID: <200307221739.h6MHdGd03573@candle.pha.pa.us> (raw)
In-Reply-To: <1058895352.4339.32.camel@gecko>


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.

---------------------------------------------------------------------------

Jord Tanner wrote:
> The Linux 2.6 kernel will have the ability to set CPU affinity for
> specific processes. There is a patch for the 2.4 kernel at
> http://www.kernel.org/pub/linux/kernel/people/rml/cpu-affinity
> 
> RedHat 9 already has support for CPU affinity build in.
> 
> The July 2003 issue of Linux Journal includes a little C program (on
> page 20) that gives you a shell level interface to the CPU affinity
> system calls, so you can dynamically assign processes to specific CPUs.
> I haven't tried it, but it looks very cool (my only SMP machine is in
> production, and I don't want to mess with it). If you try it out, please
> share your experiences with the list.
> 
> 
> Jord Tanner
> Independent Gecko Consultants
> 
> On Tue, 2003-07-22 at 10:10, SZUCS G?bor wrote:
> > "by default" -- do you mean there is a way to tell Linux to favor the second
> > real cpu over the HT one? how?
> > 
> > G.
> > ------------------------------- cut here -------------------------------
> > ----- Original Message ----- 
> > From: "Bruce Momjian" <pgman@candle.pha.pa.us>
> > Sent: Tuesday, July 22, 2003 6:26 PM
> > Subject: Re: [PERFORM] Dual Xeon + HW RAID question
> > 
> > 
> > > Right, I simplified it.  The big deal is whether the OS favors the
> > > second real CPU over one of the virtual CPU's on the same die --- by
> > > default, it doesn't.  Ever if it did work perfectly, you are talking
> > > about going from 1 to 1.4 or 2 to 2.8, which doesn't seem like much.
> > 
> > 
> > ---------------------------(end of broadcast)---------------------------
> > TIP 8: explain analyze is your friend
> -- 
> Jord Tanner <jord@indygecko.com>
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (16+ messages)  latest in thread

Message-ID: <200307221739.h6MHdGd03573@candle.pha.pa.us>
Permalink:  ../200307221739.h6MHdGd03573@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200307221739.h6MHdGd03573@candle.pha.pa.us

 · 

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: pgman@candle.pha.pa.us, jord@indygecko.com, surrano@mailbox.hu
  Subject: Re: Dual Xeon + HW RAID question
  In-Reply-To: <200307221739.h6MHdGd03573@candle.pha.pa.us>
  References: <1058895352.4339.32.camel@gecko> <200307221739.h6MHdGd03573@candle.pha.pa.us>

* 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