From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org, "Juan Casero \(FL FLC\)" <Juan.Casero@wholefoods.com>
Cc: Luke Lonergan <llonergan@greenplum.com>
Subject: Re: Sun Fire T2000 and PostgreSQL 8.1.3
Date: Wed, 05 Apr 2006 18:24:47 -0400
Message-ID: <12745.1144275887@sss.pgh.pa.us> (raw)
In-Reply-To: <200604051501.40109.josh@agliodbs.com>
References: <7583B3F1891CC0429FA4A44952AA539C66FA6D@wfm-exchprd2.wfm.pvt>
<200604051501.40109.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> Juan,
>> When I hit
>> this pgsql on this laptop with a large query I can see the load spike up
>> really high on both of my virtual processors. Whatever, pgsql is doing
>> it looks like both cpu's are being used indepently.
> Nope, sorry, you're being decieved. Postgres is strictly one process, one
> query.
This is not strictly true: we have for instance pushed off some work
into a "background writer" process, and even just having both a client
and a server process active allows some small amount of parallelism.
But you're certainly not going to see effective use of more than about
two CPUs on a single query stream ... at least not without Bizgres or
some other add-on.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, Juan.Casero@wholefoods.com, llonergan@greenplum.com
Subject: Re: Sun Fire T2000 and PostgreSQL 8.1.3
In-Reply-To: <12745.1144275887@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox