User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Tue, 08 May 2007 21:09:59 -0700
Subject: Re: Throttling PostgreSQL's CPU usage
From: "Luke Lonergan" <llonergan@greenplum.com>
To: david@lang.hm, "Carlos Moreno" <moreno_pg@mochima.com>,
	"Mark Kirkwood" <markir@paradise.net.nz>
cc: "Daniel Griscom" <griscom@suitable.com>, pgsql-performance@postgresql.org
Message-ID: <C26697A8.2F99F%llonergan@greenplum.com>
Thread-Topic: [PERFORM] Throttling PostgreSQL's CPU usage
Thread-Index: AceR7+ipJ4T6Sv3jEdu4PQAX8s8Cag==
In-Reply-To: <Pine.LNX.4.64.0705081622320.29403@asgard.lang.hm>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: 7bit

You can use the workload management feature that we've contributed to
Bizgres.  That allows you to control the level of statement concurrency by
establishing queues and associating them with roles.

That would provide the control you are seeking.

- Luke


On 5/8/07 4:24 PM, "david@lang.hm" <david@lang.hm> wrote:

> On Tue, 8 May 2007, Carlos Moreno wrote:
> 
>> Daniel Griscom wrote:
>>> 
>>>  Several people have mentioned having multiple processors; my current
>>>  machine is a uni-processor machine, but I believe we could spec the actual
>>>  runtime machine to have multiple processors/cores.
>> 
>> My estimate is that yes, you should definitely consider that.
>> 
>>>  I'm only running one query at a time; would that query be guaranteed to
>>>  confine itself to a single processor/core?
>> 
>> From what Joshua mentions, looks like you do have that guarantee.
> 
> isn't there a way to limit how many processes postgres will create?
> 
> if this is limited to 1, what happens when a vaccum run hits (or
> autovaccum)
> 
> David Lang
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>