On Wed, Oct 26, 2011 at 3:51 AM, Caleb Gray <ca...@calebgray.com> wrote: > 2) Add (or replace zlib with) LZMA. > > Some of my repositories are very large; the compression difference between > the DEFLATE algorithm and the LZMA algorithm is not negligible, and can even > be substantial. > > Recently, even the Linux kernel has officially begun using lzmalib to > compress their releases: http://www.kernel.org/pub/linux/kernel/v3.0/ (even > the difference between BZ2 and XZ is about 13M, or 31M smaller than GZ). > > A quick implementation of LZMA (by editing auto.def and blob.c's > blob_compress, blob_compress2, and blob_uncompress) resulted in the > following repository sizes for the latest trunk of SQLite: > sqlite-zlib.fossil (4.8M) (~5.0K per file) > sqlite-lzma.fossil (3.5M) (~3.6K per file) > > How's that for bandwidth efficient enough for " dial-up"?
LZMA is good for release tarballs, but has unacceptable speed and memory requirements for version control systems. Note that due to self-checks, Fossil compresses and then extracts and verifies content before committing it: http://www.fossil-scm.org/index.html/doc/trunk/www/selfcheck.wiki I'd say DEFLATE is a good compromise between LZO/SNAPPY and LZMA for our use. -- Dmitry Chestnykh _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
