From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Piotr Kublicki <Piotr(dot)Kublicki(at)iop(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: How many threads/cores Postgres can utilise? |
Date: | 2010-04-28 17:03:53 |
Message-ID: | 4BD86A79.2000409@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Scott Marlowe wrote:
> On Wed, Apr 28, 2010 at 3:15 AM, Piotr Kublicki <Piotr(dot)Kublicki(at)iop(dot)org> wrote:
>
>> Dears,
>>
>> Sorry to be a royal pain, but I cannot find it anywhere in the
>> documentation: how many threads/CPU cores Postgres v. 8.4 can utilise?
>> We're thinking about installing Postgres on a virtual machine (RedHat 5
>> 64-bits), however not sure how many CPUs can be wisely assigned, without
>> wasting of resources. Can Postgres utilise multi-core/multi-threaded
>> architecture in a reasonably extent?
>>
>
> Like Craig mentioned, each connection uses one core basically, and the
> OS can use one or maybe two. But that means that on even moderately
> busy servers 4 to 8 cores is very reasonable. On modern hardware it's
> easy to get 6 or 8 cores pretty cheaply. 2P machines can have 12 or
> 16 cores for pretty cheap too.
>
the author mentions virtual machines, where you're trying to squeeze as
much workload as possible onto those 8 or 12 cores ...
From | Date | Subject | |
---|---|---|---|
Next Message | Robert_Clift | 2010-04-28 17:39:59 | Populate arrays from multiple rows |
Previous Message | Tom Lane | 2010-04-28 17:00:58 | Re: Writing SRF |