Re: Higher TOAST compression.

Поиск
Список
Период
Сортировка
От Laurent Laborde
Тема Re: Higher TOAST compression.
Дата
Msg-id 8a1bfe660907200915r53f94b6bwb9434f6088ab770b@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Higher TOAST compression.  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Ответы Re: Higher TOAST compression.  (Laurent Laborde <kerdezixe@gmail.com>)
Список pgsql-hackers
On Mon, Jul 20, 2009 at 6:04 PM, Kevin
Grittner<Kevin.Grittner@wicourts.gov> wrote:
>
>> What about setting "PGLZ_strategy_always" as the default strategy
>> (insane cpu cost ?) ?
>> Or something in-between ?
>
> That goes beyond what I was trying to do with my recent patch.  What
> you propose may be useful, but there would need to be much discussion
> and benchmarking and it would be a new patch.
>
> If you have any benchmark information on relative speed and space
> savings, please post them.

I will try that as soon as my spare production server (2x4core Xeon,
32GB  RAM, 8 SAS Disk) is back to life.

I wasn't thinking about the very aggressive (strategy_always)
compression strategy for a default postgresql release.
Not everyone is IObound :)

But just as a default setting here at over-blog. (definitively IOBound
with large articles and comment).
Anyway, i will try and report different strategy here.

Thank you again for your feedback.

--
Laurent Laborde
Sysadmin @ http://www.over-blog.com/


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

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: Higher TOAST compression.
Следующее
От: "Kevin Grittner"
Дата:
Сообщение: Re: Review: Revise parallel pg_restore's scheduling heuristic