| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-performance(at)postgresql(dot)org, Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk> |
| Subject: | Re: Linux: more cores = less concurrency. |
| Date: | 2011-04-11 18:32:33 |
| Message-ID: | BANLkTi=Wi+DsO5Bu1kYi1GL6rECAf8M1DA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Apr 11, 2011 at 12:12 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> On Mon, 11 Apr 2011 13:09:15 -0500, "Kevin Grittner"
> <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>> Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk> wrote:
>>
>>> The new server uses 4 x 8 core Xeon X7550 CPUs at 2Ghz
>>
>> Which has hyperthreading.
>>
>>> our current servers are 2 x 4 core Xeon E5320 CPUs at 2Ghz.
>>
>> Which doesn't have hyperthreading.
>>
>> PostgreSQL often performs worse with hyperthreading than without.
>> Have you turned HT off on your new machine? If not, I would start
>> there.
>
> And then make sure you aren't running CFQ.
>
> JD
This++
Also if you're running a good hardware RAID controller, jsut go to NOOP
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-04-11 18:39:03 | Re: Multiple index builds on same table - in one sweep? |
| Previous Message | Glyn Astill | 2011-04-11 18:23:50 | Re: Linux: more cores = less concurrency. |