From: | "Jean-Yves F(dot) Barbier" <12ukwn(at)gmail(dot)com> |
---|---|
To: | "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: limiting resources to users |
Date: | 2009-11-25 18:40:29 |
Message-ID: | 4B0D7A1D.8030208@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Gauthier, Dave a écrit :
> Hi:
>
>
>
> Is there a way in Postgres to limit how much cpu, memory, other
> resources a certain DB gets? A MySQL DB that I’m now replacing with PG
> has been having problems with run-away users that pound one DB with
> intense processes running periodically in cron jobs. The effect is that
> it takes up all the resources and the users of other DBs suffer because
> the CPU is pegged servicing the first guy..
>
>
>
> The PG versio will have one PG instance with many DBs. One set of these
> DBs are vital for operations and should have the highest priority.
> Another set of DBs are not vital but their users are the culprits that
> consume all the resources. I want to give DBs A, B, and C the highest
> priority, DBs D, E, F the lowest. If a DB F user is taking up all the
> resources, and a DB B users runs a query, I want to service the DB B
> guys first and backburner the DB F guy until the DB B guy is serviced first.
Buy a chainsaw and cut one hand from each user (Ok --->[])
May be you can play with renice (or even with the -N switch in
start-stop-daemon, but I don't know if it is a regular package
or just a Debian one).
As nice allow running from -20 to +20 priority, it shall give you
the pliability you need: as soon as the higher reniced daemon will
claim power the system will grant him against other process.
JY
--
There is no sincerer love than the love of food.
-- George Bernard Shaw
From | Date | Subject | |
---|---|---|---|
Next Message | Yadira Lizama Mue | 2009-11-25 18:49:35 | change of oid values? |
Previous Message | Postgres User | 2009-11-25 18:20:42 | Postgres database performance on 6 core Opteron vs 4 core Xeon |