Re: CPU killer

From: Tod McQuillin <devin(at)spamcop(dot)net>
To: Vilson farias <vilson(dot)farias(at)digitro(dot)com(dot)br>
Cc: pgsql-general(at)hub(dot)org, SIMONE Carla MOSENA <simone(dot)mosena(at)digitro(dot)com(dot)br>
Subject: Re: CPU killer
Date: 2000-10-28 05:42:29
Message-ID: Pine.GSO.4.21.0010280040060.6023-100000@sysadmin
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 27 Oct 2000, Vilson farias wrote:

> I've been using Postgres in a Pentium 75Mhz, Linux RedHat 6.2, 32Mb.
>
> Every big query I execute uses too much cpu (more than 90%).
>
> I start postgres with these params: su -l postgres -c
> '/usr/bin/postmaster -B 2048 -i -D "/home/postgres/data"' &.
>
> What should I do for avoid postgres extreme cpu allocation? I know
> sometimes non-indexed tables or huge size tables can be slow, but here
> I don't care about execution speed, I just want less cpu allocation no
> matter how slow.

Well, assuming you've already optimised the queries to run as quickly as
possible, if you don't want the backend stealing cpu from other processes
then start postmaster with the nice command (man nice) to give it a lower
priority. It will still use just as much CPU time, but not at the expense
of other processes.
--
Tod McQuillin

In response to

  • CPU killer at 2000-10-27 21:12:57 from Vilson farias

Browse pgsql-general by date

  From Date Subject
Next Message Radhakrishnan R. 2000-10-28 06:49:32 set digest pgsql-general
Previous Message Isaac 2000-10-28 05:39:48 Re: newbie question: ERROR: getattproperties: no attribute tuple 1259 -2