From: Bruce Momjian <pgman@candle.pha.pa.us>
To: SZUCS Gábor <surrano@mailbox.hu>
Cc: pgsql-performance@postgresql.org
Subject: Re: Dual Xeon + HW RAID question
Date: Mon, 21 Jul 2003 15:07:32 -0400 (EDT)
Message-ID: <200307211907.h6LJ7YV03382@candle.pha.pa.us> (raw)
In-Reply-To: <00b901c34f49$1ed04b40$0403a8c0@fejleszt4>
SZUCS Gábor wrote:
> Alexandre,
>
> I missed your orig. post, but AFAIK multiprocessing kernels will handle HT
> CPUs as 2 CPUs each. Thus, our dual Xeon 2.4 is recognized as 4 Xeon 2.4
> CPUs.
>
> This way, I don't think HT would improve any single query (afaik no postgres
> process uses more than one cpu), but overall multi-query performance has to
> improve.
When you use hyperthreading, each virtual cpu runs at 70% of a full CPU,
so hyperthreading could be slower than non-hyperthreading. On a fully
loaded dual cpu system, you are looking at 2.8 cpu's (0.70 * 4), while
if it isn't loaded, you are looking at slowing down if you are only
using 1 or 2 cpu's.
--
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
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, surrano@mailbox.hu
Subject: Re: Dual Xeon + HW RAID question
In-Reply-To: <200307211907.h6LJ7YV03382@candle.pha.pa.us>
References: <00b901c34f49$1ed04b40$0403a8c0@fejleszt4> <200307211907.h6LJ7YV03382@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