Message-ID: <4640FDD2.9070304@mochima.com>
Date: Tue, 08 May 2007 18:46:42 -0400
From: Carlos Moreno <moreno_pg@mochima.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070326)
MIME-Version: 1.0
CC: pgsql-performance@postgresql.org
Subject: Re: Throttling PostgreSQL's CPU usage
References: <p0624080bc266892a91b2@[192.168.1.8]>
	<20070508205120.GA7983@uio.no> <4640FA6E.4050003@mochima.com>
	<4640FC3B.3000608@commandprompt.com>
In-Reply-To: <4640FC3B.3000608@commandprompt.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Joshua D. Drake wrote:
> Am I missing something??  There is just *one* instance of this idea 
> in, what,
>> four replies??  I find it so obvious, and so obviously the only 
>> solution that
>> has any hope to work, that it makes me think I'm missing something ...
>>
>> Is it that multiple PostgreSQL processes will end up monopolizing as 
>> many
>> CPU cores as you give it?  (ok, that would suck, for sure  :-))
>
> PostgreSQL is process based, so if you have one query that is eating a 
> lot of cpu, it is only one cpu... you would have another for your 
> render to run on.

There is still the issue that there could be several (many?) queries 
running
concurrently --- but that's much easier to control at the application 
level;
so maybe simply using a multi-CPU/multi-core hardware would be the
simplest solution?

Carlos
--