From: Luke Lonergan <llonergan@greenplum.com>
To: david@lang.hm, "Carlos Moreno" <moreno_pg@mochima.com>
To: Mark Kirkwood <markir@paradise.net.nz>
Cc: Daniel Griscom <griscom@suitable.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Throttling PostgreSQL's CPU usage
Date: Tue, 08 May 2007 21:09:59 -0700
Message-ID: <C26697A8.2F99F%llonergan@greenplum.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705081622320.29403@asgard.lang.hm>
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
>
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, moreno_pg@mochima.com, markir@paradise.net.nz, griscom@suitable.com
Subject: Re: Throttling PostgreSQL's CPU usage
In-Reply-To: <C26697A8.2F99F%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