Hi all,
I was just reading
http://blogs.sun.com/dap/entry/zfs_compression
and would like to know what the experience of people is about enabling
compression in ZFS.
In principle I don't think it's a bad thing, especially not when the
CPUs are fast enough to improve the performance as the hard
Carsten Aulbert wrote:
Hi all,
I was just reading
http://blogs.sun.com/dap/entry/zfs_compression
and would like to know what the experience of people is about enabling
compression in ZFS.
In principle I don't think it's a bad thing, especially not when the
CPUs are fast enough to improve the
Hi Richard,
Richard Elling wrote:
Files are not compressed in ZFS. Blocks are compressed.
Sorry, yes, I was not specific enough.
If the compression of the blocks cannot gain more than 12.5% space savings,
then the block will not be compressed. If your file contains
compressable parts
On Mon, Mar 16, 2009 at 10:34:54PM +0100, Carsten Aulbert wrote:
Can ZFS make educated guesses where the seek targets might be or will it
read the file block by block until it reaches the target position, in
the latter case it might be quite inefficient if the file is huge and
has a large
On Mon, Mar 16, 2009 at 09:54:57PM +0100, Carsten Aulbert wrote:
o what happens when a user opens the file and does a lot of seeking
inside the file? For example our scientists use a data format where
quite compressible data is contained in stretches and the file header
contains a dictionary
Carsten Aulbert wrote:
Hi Richard,
Richard Elling wrote:
Files are not compressed in ZFS. Blocks are compressed.
Sorry, yes, I was not specific enough.
If the compression of the blocks cannot gain more than 12.5% space savings,
then the block will not be compressed. If your
Darren, Richard,
thanks a lot for the very good answers. Regarding the seeking I was
probably mislead by the believe that the block size was like an
impenetrable block where as much data as possible is being squeezed into
(like .Z files would be if you first compressed and then cut the data
into
