Skip site navigation (1) Skip section navigation (2)

Re: Vacuum rate limit in KBps

From: Jim Nasby <jim(at)nasby(dot)net>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Vacuum rate limit in KBps
Date: 2012-01-18 02:00:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Jan 15, 2012, at 8:13 PM, Greg Smith wrote:
> On 01/15/2012 04:17 PM, Heikki Linnakangas wrote:
>> I think it makes more sense to use the max read rate as the main knob, rather than write rate. That's because the max read rate is higher than the write rate, when you don't need to dirty pages. Or do you think saturating the I/O system with writes is so much bigger a problem than read I/O that it makes more sense to emphasize the writes?
> I haven't had the I/O rate logging available for long enough to have a good feel for which is more important to emphasize.  I'm agnostic on this.  I'd have no problem accepting the argument that exposing the larger of the two rates--which is the read one--makes for a cleaner UI.  Or that it is the one more like other knobs setting precedents here.

Could we expose both?

On our systems writes are extremely cheap... we don't do a ton of them (relatively speaking), so they tend to just fit into BBU cache. Reads on the other hard are a lot more expensive, at least if they end up actually hitting disk. So we actually set page_dirty and page_hit the same.
Jim C. Nasby, Database Architect                   jim(at)nasby(dot)net
512.569.9461 (cell)               

In response to


pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2012-01-18 02:46:36
Subject: Re: automating CF submissions (was xlog location arithmetic)
Previous:From: Fujii MasaoDate: 2012-01-18 01:56:46
Subject: Re: Patch review for logging hooks (CF 2012-01)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group