Re: Vacuum rate limit in KBps

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Vacuum rate limit in KBps
Дата
Msg-id CA+U5nML_cu_1xdka+Vi5oRHLxkRQL3Qez42c7hQg9LCoSPDDhg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Vacuum rate limit in KBps  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Ответы Re: Vacuum rate limit in KBps  (Alvaro Herrera <alvherre@commandprompt.com>)
Список pgsql-hackers
On Sun, Jan 15, 2012 at 9:17 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> 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?

Yes, the writes are more important of the two.

Too many writes at one time can overflow hardware caches, so things
tend to get much worse beyond a certain point.

Also, rate limiting writes means we rate limit WAL rate also which is
very important.

I'd like this to apply to large DDL, not just VACUUMs.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Review of patch renaming constraints
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: automating CF submissions (was xlog location arithmetic)