Jim Starkey wrote:

<..snip..>

>
> I originally had in mind using blob filters for compression, but that
> really hasn't panned out. On the other hand, blob compression is a good
> thing, and almost always useful (the exception is where it is already
> compressed). It does take cycles to compress and decompress, but cycles
> are increasing much faster than disk bandwidth.
>
> The more I think about, the more I think that blobs should always be
> stored compressed, but that compression/decompression be performed
> primarily on the client side. The implication is that the plumbing
> needs to be compression aware at least at the lower levels of the API.
> If we're going to build in end to end compression, we pretty much need
> to standardize on a single compression schema, and zlib is the obvious
> candidate.
>
> Now, having taken a position, can we have the opposing opinion from Dmitry?
>

I don't know what kind of blobs you are storing in the database.
In my case I'm only storing JPG's in which case it's a complete
waste of time to try to compress them.

Steen