| From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rod Taylor <rbt(at)rbt(dot)ca> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Pgsql Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Capping CPU usage? |
| Date: | 2002-12-12 17:43:25 |
| Message-ID: | web-2278796@davinci.ethosmedia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Tom,
> If the issue is to prevent Postgres *as a whole* from hogging CPU
> usage,
> I would think that nice-ing the postmaster at launch would work
> beautifully. Requests like "I want Postgres to use no more than 30%
> of CPU" make no sense to me: if the CPU is otherwise idle, why should
> you insist on reserving 70% of it for the idle loop?
<grin> That's what I asked the person who asked me. Apparently, they
want to do real-time operations without forking out for a real-time OS.
My response was "you can nice the postmaster, and simplify your
queries, but that's about it".
Thank you, everybody, for confirming this.
-Josh Berkus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2002-12-12 17:49:08 | Re: Time to commit a change |
| Previous Message | Stephan Szabo | 2002-12-12 17:15:43 | Re: Time to commit a change |