From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Shane Ambler" <pgsql(at)sheeky(dot)biz> |
Cc: | "Semi Noob" <seminoob(at)gmail(dot)com>, "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Need for help! |
Date: | 2008-05-15 17:59:40 |
Message-ID: | dcc563d10805151059n54d652e0xcc88b3459471730f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, May 15, 2008 at 11:08 AM, Shane Ambler <pgsql(at)sheeky(dot)biz> wrote:
> Semi Noob wrote:
>
>> My CPU is 2CPU: Intel(R) Xeon(TM) CPU 3.20GHz. Disk: disk system is
>> RAID-5;
>
> Early versions of postgresql had issues with P4 HT CPU's but I believe they
> have been resolved.
>
> I am quite certain that it only related to the early P4's not the Xeon.
The real problem was with the various OS kernels not know how to treat
a HT "core" versus a real core. Linux in particular was a bad
performer with HT turned on, and pgsql made it suffer more than many
other apps for not knowing the difference. The linux kernel has known
for some time now how to treat a HT core properly.
From | Date | Subject | |
---|---|---|---|
Next Message | Justin | 2008-05-15 18:18:09 | Re: Need for help! |
Previous Message | Eliot, Christopher | 2008-05-15 17:11:13 | Re: Populating a sparse array piecemeal in plpgsql |