From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Jeff <threshar@torgo.978.org>
Cc: Christopher Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Perfomance Tuning
Date: Thu, 14 Aug 2003 17:47:01 -0400 (EDT)
Message-ID: <200308142147.h7ELl1Q11939@candle.pha.pa.us> (raw)
In-Reply-To: <Pine.BSF.4.44.0308140824240.21661-100000@torgo.978.org>
Jeff wrote:
> > You raise a good point vis-a-vis the thought of spawning multiple
> > readers; that could conceivably be a useful approach to improve
> > performance for very large queries. If you could "stripe" the tables
> > in some manner so they could be doled out to multiple worker
> > processes, that could indeed provide some benefits. If there are
> > three workers, they might round-robin to grab successive pages from
> > the table to do their work, and then end with a merge step.
>
> The way informix does this is two fold:
> 1. it handles the raw disks, it knows where table data is
> 2. it can "partition" tables in a number of ways: round robin,
> concatination or expression (Expression is nifty, allows you to use a
> basic "where" clause to decide where to put data. ie
> create table foo (
> a int,
> b int,
> c int ) fragment on c > 0 and c < 100 in dbspace1, c > 100 c < 200 in
> dbspace 2;
>
> that kind of thing.
> and yeah, I would not expect to see it for a long time.. Without threading
> it would be rather difficult to implement.. but who knows what the future
> will bring us.
The big question is whether the added complexity is worth it. I know
Informix 5 was faster than Informix 7 on single CPU machines for quite a
while. It might still be true.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: pgman@candle.pha.pa.us, threshar@torgo.978.org, cbbrowne@acm.org
Subject: Re: Perfomance Tuning
In-Reply-To: <200308142147.h7ELl1Q11939@candle.pha.pa.us>
References: <Pine.BSF.4.44.0308140824240.21661-100000@torgo.978.org> <200308142147.h7ELl1Q11939@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