From: Sam Vilain <sam@vilain.net>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: Decompression speed: zip vs lzo
Date: Thu, 10 Jan 2008 12:23:17 +1300 [thread overview]
Message-ID: <47855765.9090001@vilain.net> (raw)
In-Reply-To: <7v4pdmfw27.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
> Note that the space nor time performance of compressing and
> uncompressing a single huge blob is not as interesting in the
> context of git as compressing/uncompressing millions of small
> pieces whose total size is comparable to the specimen of "huge
> single blob" experiment. Obviously loose object files are
> compressed individually, and packfile contents are also
> individually and independently compressed. Set-up cost for
> individual invocation of compression and uncompression on
> smaller data matters a lot more than an experiment on
> compressing and uncompressiong a single huge blob (this applies
> to both time and space).
Yes - and lzo will almost certainly win on all those counts!
I think to go forward this would need a prototype and benchmark figures
for things like "annotate" and "fsck --full" - but bear in mind it would
be a long road to follow-up to completion, as repository compatibility
would need to be a primary concern and this essentially would create a
new pack type AND a new *object* type. Not only that, but currently
there is no header in the objects on disk which can be used to detect a
gzip vs. an lzop stream. Not really worth it IMHO - gzip is already
fast enough on even the most modern processor these days.
Sam.
next prev parent reply other threads:[~2008-01-09 23:23 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 22:01 Decompression speed: zip vs lzo Marco Costalba
2008-01-09 22:55 ` Junio C Hamano
2008-01-09 23:23 ` Sam Vilain [this message]
2008-01-09 23:31 ` Johannes Schindelin
2008-01-10 1:02 ` Sam Vilain
2008-01-10 5:02 ` Sam Vilain
2008-01-10 9:16 ` Pierre Habouzit
2008-01-10 20:39 ` Nicolas Pitre
2008-01-10 21:01 ` Linus Torvalds
2008-01-10 21:30 ` Nicolas Pitre
2008-01-11 8:57 ` Pierre Habouzit
2008-01-10 21:45 ` Sam Vilain
2008-01-10 22:03 ` Linus Torvalds
2008-01-10 22:28 ` Sam Vilain
2008-01-10 22:56 ` Linus Torvalds
2008-01-11 1:01 ` Sam Vilain
2008-01-11 2:10 ` Linus Torvalds
2008-01-11 6:29 ` Sam Vilain
2008-01-11 7:05 ` Sam Vilain
2008-01-11 16:03 ` Linus Torvalds
2008-01-12 1:52 ` Sam Vilain
2008-01-12 2:32 ` Nicolas Pitre
2008-01-12 3:06 ` Sam Vilain
2008-01-12 16:09 ` Nicolas Pitre
2008-01-12 16:44 ` Johannes Schindelin
2008-01-12 4:46 ` Junio C Hamano
2008-01-10 21:51 ` Marco Costalba
2008-01-10 22:01 ` Sam Vilain
2008-01-10 22:18 ` Nicolas Pitre
2008-01-11 9:45 ` Pierre Habouzit
2008-01-11 14:27 ` Nicolas Pitre
2008-01-11 14:18 ` Morten Welinder
2008-01-10 3:41 ` Nicolas Pitre
2008-01-10 6:55 ` Marco Costalba
2008-01-10 11:45 ` Marco Costalba
2008-01-10 12:12 ` Johannes Schindelin
2008-01-10 12:18 ` Marco Costalba
2008-01-10 19:34 ` Dana How
2008-01-09 23:49 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47855765.9090001@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mcostalba@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).