From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Background vacuum |
Date: | 2007-05-19 05:27:16 |
Message-ID: | Pine.GSO.4.64.0705190100570.29971@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Fri, 18 May 2007, Ron Mayer wrote:
> Anecdotally ;-) I've found renice-ing reports to help
Let's break this down into individual parts:
1) Is there enough CPU-intensive activity in some database tasks that they
can be usefully be controlled by tools like nice? Sure.
2) Is it so likely that you'll fall victim to a priority inversion problem
that you shouldn't ever consider that technique? No.
3) Does the I/O scheduler in modern OSes deal with a lot more things than
just the CPU? You bet.
4) Is vacuuming a challenging I/O demand? Quite.
Add all this up, and that fact that you're satisfied with how nice has
worked successfully for you doesn't have to conflict with an opinion that
it's not the best approach for controlling vacuuming. I just wouldn't
extrapolate your experience too far here.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Sergei Shelukhin | 2007-05-19 10:22:18 | Re: any way to get rid of Bitmap Heap Scan recheck? |
Previous Message | Greg Smith | 2007-05-19 05:00:00 | Re: 121+ million record table perf problems |