| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Steve Atkins <steve(at)blighty(dot)com> |
| Cc: | pgsql General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Are there plans to add data compression feature to postgresql? |
| Date: | 2008-10-30 05:43:29 |
| Message-ID: | 49094981.2050502@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Steve Atkins wrote:
>
> On Oct 29, 2008, at 9:50 PM, Grant Allen wrote:
>>
>>
>> One other thing I forgot to mention: Compression by the DB trumps
>> filesystem compression in one very important area - shared_buffers!
>> (or buffer_cache, bufferpool or whatever your favourite DB calls its
>> working memory for caching data). Because the data stays compressed
>> in the block/page when cached by the database in one of its buffers,
>> you get more bang for you memory buck in many circumstances! Just
>> another angle to contemplate :-)
>
> The additional latency added by decompression is reasonably small
> compared with traditional disk access time. It's rather large compared
> to memory access time.
The one place where Compression is an immediate benefit is the wire. It
is easy to forget that one of our number one bottlenecks (even at
gigabit) is the amount of data we are pushing over the wire.
Joshua D. Drake
>
> Cheers,
> Steve
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Atkins | 2008-10-30 05:52:51 | Re: Are there plans to add data compression feature to postgresql? |
| Previous Message | Steve Atkins | 2008-10-30 05:26:26 | Re: Are there plans to add data compression feature to postgresql? |