From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Chris Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Scaling up PostgreSQL in Multiple CPU / Dual Core
Date: Sun, 9 Apr 2006 16:24:44 -0400 (EDT)
Message-ID: <200604092024.k39KOjR15478@candle.pha.pa.us> (raw)
In-Reply-To: <60r74rskn2.fsf@dba2.int.libertyrms.com>
Added to TODO:
* Experiment with multi-threaded backend better resource utilization
This would allow a single query to make use of multiple CPU's or
multiple I/O channels simultaneously.
---------------------------------------------------------------------------
Chris Browne wrote:
> mstone+postgres@mathom.us (Michael Stone) writes:
>
> > On Fri, Mar 24, 2006 at 01:21:23PM -0500, Chris Browne wrote:
> >>A naive read on this is that you might start with one backend process,
> >>which then spawns 16 more. Each of those backends is scanning through
> >>one of those 16 files; they then throw relevant tuples into shared
> >>memory to be aggregated/joined by the central one.
> >
> > Of course, table scanning is going to be IO limited in most cases, and
> > having every query spawn 16 independent IO threads is likely to slow
> > things down in more cases than it speeds them up. It could work if you
> > have a bunch of storage devices, but at that point it's probably
> > easier and more direct to implement a clustered approach.
>
> All stipulated, yes. It obviously wouldn't be terribly useful to scan
> more aggressively than I/O bandwidth can support. The point is that
> this is one of the kinds of places where concurrent processing could
> do some good...
> --
> let name="cbbrowne" and tld="acm.org" in name ^ "@" ^ tld;;
> http://cbbrowne.com/info/spiritual.html
> Save the whales. Collect the whole set.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
Bruce Momjian http://candle.pha.pa.us
+ If your life is a hard drive, Christ can be your backup. +
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: pgman@candle.pha.pa.us, cbbrowne@acm.org
Subject: Re: Scaling up PostgreSQL in Multiple CPU / Dual Core
In-Reply-To: <200604092024.k39KOjR15478@candle.pha.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