Re: [HACKERS] Changing the default configuration

Поиск
Список
Период
Сортировка
От Daniel Kalchev
Тема Re: [HACKERS] Changing the default configuration
Дата
Msg-id 200302140755.h1E7tCY04481@dcave.digsys.bg
обсуждение исходный текст
Ответ на Re: [HACKERS] Changing the default configuration  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-advocacy
>>>Bruce Momjian said:
 >
 > I imagined they could run pgtune anytime after install to update those
 > performance parameters.  It gives them a one-stop location to at least
 > do minimal tuning, and as their load changes, they can run it again.

True, but to make reasonably good choice, they will need to base the parameter
selection on some statistics data. Not many people do trough testing before
tuning their system and in many cases, the tests one do rarely resemble the
real-world usage of their database(s).

I agree that pgtune would be wonderful tool in this case, but they first need
to get some idea what parameters should be given to it.

This process if further complicated by the fact that we can tune PostgreSQL on
a per-installation basis, instead of on per-database basis - many of the
parameters, for example FSM and sort memory are database related. We usually
split data into databases to put related data together or data with similar
usage pattern etc.

Daniel


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

Предыдущее
От: Kevin Brown
Дата:
Сообщение: Re: [HACKERS] Changing the default configuration (was Re:
Следующее
От: Daniel Kalchev
Дата:
Сообщение: Re: [HACKERS] Changing the default configuration