From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "c k" <shreeseva(dot)learning(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Multi-processors |
Date: | 2008-09-19 14:29:32 |
Message-ID: | dcc563d10809190729g1cd2679bo79a0d40980cdb293@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, Sep 19, 2008 at 5:55 AM, c k <shreeseva(dot)learning(at)gmail(dot)com> wrote:
> Hello PG Community,
> Does PG uses multiple processors/cores if available by default on various
> OSes?
Yes, see attached top extract from my primary db server at work
> What are the limitations on using multiple processors/cores and main
> memory?
Do you mean how many CPUs and how much memory? no real limits on a 64
bit machine. Note that it's often better to let the os do the majority
of caching, depending on your work load. This is especially true in
OLTP where the cost of pgsql maintaining a large buffer is higher than
the benefit it provides, but the kernel can cache much larger datasets
faster, in my experience.
Attachment | Content-Type | Size |
---|---|---|
db-top.txt | text/plain | 3.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-09-19 14:39:14 | Re: Regaining superuser access |
Previous Message | Kevin Grittner | 2008-09-19 13:52:18 | Re: Multi-processors |