Re: Any risk in increasing BLCKSZ to get larger tuples?

Поиск
Список
Период
Сортировка
От Steve Wolfe
Тема Re: Any risk in increasing BLCKSZ to get larger tuples?
Дата
Msg-id 003401c03a1b$91da3a60$50824e40@iboats.com
обсуждение исходный текст
Ответ на Any risk in increasing BLCKSZ to get larger tuples?  (Philip Hallstrom <philip@adhesivemedia.com>)
Список pgsql-general
> In some cases yes, in some no.  Simple text should compress/decompress
> quickly and the cpu time wasted is made up for by less hardware access
> time and smaller db files.  If you have a huge database the smaller db
> files could be critical.

  Hmm... that doesn't seem quite right to me.  Whether it is compressed or
not, the same amount of final data has to move across the system bus to the
CPU for processing.  It's the difference of (A) moving a large amount of
data to the CPU and processing it, or (B) moving a small amount of data to
the CPU, use the CPU cycles to turn it into the large set (as large as in
(A)), then processing it.  I could be wrong, though.

steve



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

Предыдущее
От: KuroiNeko
Дата:
Сообщение: RE: MySQL -> pgsql
Следующее
От: Joseph Shraibman
Дата:
Сообщение: Re: A stupid question :)