Hardware Config

Started by Rich Bowmanalmost 25 years ago4 messagesgeneral
Jump to latest
#1Rich Bowman
richb@bennettsupply.com

Will PostgreSQL take advantage of more than 1 CPU? If so, are there any
benchmarks showing how it scales with multiple CPUs?

--
Rich Bowman
Bennett Supply Company
richb@bennettsupply.com

#2Thalis A. Kalfigopoulos
thalis@cs.pitt.edu
In reply to: Rich Bowman (#1)
Re: Hardware Config

From a previous thread, I remember being said that it is mostly an OS issue. So if you make your OS kernel aware of your multiple CPUs, Pg will be just fine.

cheers,
thalis

On Thu, 14 Jun 2001, Rich Bowman wrote:

Show quoted text

Will PostgreSQL take advantage of more than 1 CPU? If so, are there any
benchmarks showing how it scales with multiple CPUs?

--
Rich Bowman
Bennett Supply Company
richb@bennettsupply.com

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

#3Steve Wolfe
steve@iboats.com
In reply to: Thalis A. Kalfigopoulos (#2)
Re: Hardware Config

Will PostgreSQL take advantage of more than 1 CPU? If so, are there

any

benchmarks showing how it scales with multiple CPUs?

We run PG on a quad xeon, and it works wonderfully. From PG's design
of forking off a new backend for each connection, it is inherantly
scalable, as each backend can run on another CPU. And, of course, having
extra CPU's to handle kernel code, I/O, interrupts, and other things is
always good.

steve

#4Richard Huxton
dev@archonet.com
In reply to: Thalis A. Kalfigopoulos (#2)
Re: Hardware Config

From: "Steve Wolfe" <steve@iboats.com>

Will PostgreSQL take advantage of more than 1 CPU? If so, are there

any

benchmarks showing how it scales with multiple CPUs?

We run PG on a quad xeon, and it works wonderfully. From PG's design
of forking off a new backend for each connection, it is inherantly
scalable, as each backend can run on another CPU. And, of course, having
extra CPU's to handle kernel code, I/O, interrupts, and other things is
always good.

Although the original poster should know that it won't spread the cost of
one large query over several CPU's (which I believe Oracle can be made to
do).

- Richard Huxton