| From: | Jim Nasby <jim(at)nasby(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: really lazy vacuums? |
| Date: | 2011-03-21 18:08:04 |
| Message-ID: | 1CA5FCA1-5E17-44F6-8A7D-02B24C104D61@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mar 16, 2011, at 7:44 PM, Robert Haas wrote:
> It
> would be really nice (for this and for other things) if we had some
> way of measuring the I/O saturation of the system, so that we could
> automatically adjust the aggressiveness of background processes
> accordingly.
Has anyone looked at the overhead of measuring how long IO requests to the kernel take? If we did that not only could we get an idea of what our IO workload looked like, we could also figure out whether a block came out of cache or not. That information could potentially be useful to the planner, but even if the database couldn't use that knowledge itself it would be a damn useful statistic to have... IMHO, far more useful than our current hit rate statistics.
--
Jim C. Nasby, Database Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-03-21 18:51:03 | Re: Missing semicolon in parser's gram.y |
| Previous Message | Bernd Helmle | 2011-03-21 17:44:51 | psql \dt and table size |