From: | Adrian 'Dagurashibanipal' von Bidder <avbidder(at)fortytwo(dot)ch> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Options for growth |
Date: | 2003-01-16 16:59:19 |
Message-ID: | 1042736358.2269.133.camel@altfrangg.fortytwo.ch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2003-01-16 at 17:42, D'Arcy J.M. Cain wrote:
> We are also looking at hardware solutions, multi-CPU PCs with tons (24GB) of
> memory. I know that memory will improve access if it prevents swapping but
> how well does PostgreSQL utilize multiple CPUs?
At most one CPU is used for any single postgres backend (that means for
any single database connection). So, if your load problem is single
queries being too slow, thee's nothing you can do with adding more CPUs.
If your problem is many connections maxing out the db, PostgreSQL can
take full advantage of multiple CPUs.
Of course, most db apps still are not cpu bound, so you'd have to do
some careful benchmarking first or you'll be spending too much money.
cheers
-- vbi
--
get my gpg key here: http://fortytwo.ch/gpg/92082481
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2003-01-16 17:23:52 | Re: Options for growth |
Previous Message | Ross J. Reedstrom | 2003-01-16 16:50:49 | Re: Oracle rant |