From: Luke Lonergan <llonergan@greenplum.com>
To: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: Scaling up PostgreSQL in Multiple CPU / Dual Core
Date: Fri, 24 Mar 2006 07:02:15 -0800
Message-ID: <C04949F7.1FF9B%llonergan@greenplum.com> (raw)
In-Reply-To: <87hd5olgyd.fsf@wolfe.cbbrowne.com>
Christopher,
On 3/23/06 6:22 PM, "Christopher Browne" <cbbrowne@acm.org> wrote:
> Question: Does the Bizgress/MPP use threading for this concurrency?
> Or forking?
>
> If it does so via forking, that's more portable, and less dependent on
> specific complexities of threading implementations (which amounts to
> non-portability ;-)).
OK - I'll byte:
It's process based, we fork backends at slice points in the execution plan.
To take care of the startup latency problem, we persist sets of these
backends, called "gangs". They appear, persist for connection scope for
reuse, then are disbanded.
> Most times Jan comes to town, we spend a few minutes musing about the
> "splitting queries across threads" problem, and dismiss it again; if
> there's the beginning of a "split across processes," that's decidedly
> neat :-).
:-)
- Luke
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: llonergan@greenplum.com, cbbrowne@acm.org
Subject: Re: Scaling up PostgreSQL in Multiple CPU / Dual Core
In-Reply-To: <C04949F7.1FF9B%llonergan@greenplum.com>
* 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