| From: | "Richard Huxton" <dev(at)archonet(dot)com> |
|---|---|
| To: | "Dirk Lutzebaeck" <lutzeb(at)aeccom(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Load balancing lots of simultaneous clients or queries? |
| Date: | 2001-05-22 08:56:42 |
| Message-ID: | 00db01c0e29d$1fb6f240$1001a8c0@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
From: "Dirk Lutzebaeck" <lutzeb(at)aeccom(dot)com>
> It would be nice if a client could say: hey I know I have a large task
> / query please set me to a low priority. So the server would withdraw some
> cpu and io cycles from this task.
>
> On a per process basis one would do this with 'nice' but how could
> that be applied to the postmaster/postgres mechanism?
> Something like SET PRIORITY...
>
> Any comments?
Problem I can see is when you have interdependent transactions. If task A
takes longer to commit it could hold up everyone waiting on it.
On the other hand - I can see where you're coming from for large selects
(weekly summary reports - that sort of thing).
- Richard Huxton
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heinrich Retzlaw | 2001-05-22 09:24:21 | lo_open, lo_read etc in embedded sql |
| Previous Message | Richard Huxton | 2001-05-22 08:49:46 | Re: Select statement |