From: Mark Kirkwood <markir@paradise.net.nz>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org, Andreas Kostyrka <andreas@kostyrka.org>
Cc: Carlos H. Reimer <carlos.reimer@opendb.com.br>
Cc: Jim C. Nasby <jim@nasby.net>
Cc: Brad Nicholson <bnichols@ca.afilias.info>
Subject: Re: RES: Priority to a mission critical transaction
Date: Wed, 29 Nov 2006 14:11:12 +1300
Message-ID: <456CDE30.4010502@paradise.net.nz> (raw)
In-Reply-To: <200611281145.44277.josh@agliodbs.com>
References: <20061127005143.GJ39519@nasby.net>
<PEEPKDFEHHEMKBBFPOOKMEAIDKAA.carlos.reimer@opendb.com.br>
<20061128192036.GB7489@andi-lap.la.revver.com>
<200611281145.44277.josh@agliodbs.com>
Josh Berkus wrote:
> All,
>
> The Bizgres project is working on resource management for PostgreSQL. So far,
> however, they have been able to come up with schemes that work for BI/DW at
> the expense of OLTP. Becuase of O^N lock checking issues, resource
> management for OLTP which doesn't greatly reduce overall performance seems a
> near-impossible task.
>
Right - I guess it is probably more correct to say that the
implementation used in Bizgres is specifically targeted at BI/DW
workloads rather than OLTP.
At this point we have not measured its impact on concurrency in anything
other than a handwaving manner - e.g pgbench on an older SMP system
showed what looked like about a 10% hit. However the noise level for
pgbench is typically >10% so - a better benchmark on better hardware is
needed.
Cheers
Mark
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: markir@paradise.net.nz, josh@agliodbs.com, andreas@kostyrka.org, carlos.reimer@opendb.com.br, jim@nasby.net, bnichols@ca.afilias.info
Subject: Re: RES: Priority to a mission critical transaction
In-Reply-To: <456CDE30.4010502@paradise.net.nz>
* 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