Re: worse than expected compression ratios with -o compress

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Mon, 18 Jan 2010, Chris Mason wrote:

Currently the only compression algorithm we support is gzip, so try gzipp'ing
your database to get a better comparison.  The plan is to eventually support
other compression algorithms, but currently we do not.  Thanks,

The compression code backs off compression pretty quickly if parts of
the file do not compress well.  This is another way of saying it favors
CPU time over the best possible compression.  If gzip ends up better
than what you're getting from btrfs, I can give you a patch to force
compression all the time.

Yes, gzip compresses much better than btrfs. I'd greatly appreciate a patch to force compression all the time.

It would be nice if such an ability were merged in the mainline. Perhaps there could be a mount option or tunable parameter to force compression?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux