From: Andreas Ericsson <ae@op5.se>
To: Nicolas Pitre <nico@cam.org>
Cc: Marco Costalba <mcostalba@gmail.com>,
Jon Smirl <jonsmirl@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Why SHA are 40 bytes? (aka looking for flames)
Date: Tue, 24 Apr 2007 17:18:18 +0200 [thread overview]
Message-ID: <462E1FBA.9020109@op5.se> (raw)
In-Reply-To: <alpine.LFD.0.98.0704241058490.12375@xanadu.home>
Nicolas Pitre wrote:
> On Tue, 24 Apr 2007, Andreas Ericsson wrote:
>
>> Using a more efficient compression algorithm for the objects
>> themselves (bzip2, anyone?) will most likely reduce storage size an
>> order of magnitude more than reducing the size of the hash, although
>> at the expense of CPU-efficiency.
>
> An order of magnitude I really doubt it. Maybe 20% could be a really
> optimistic prediction. But if bzip2 could reduce the repo by 20%, it
> will slow runtime usage of that repo by maybe 100%. That is not worth
> it.
>
> This is also the reason why we changed the default zlib compression
> level from "best" to "default".
>
... order of magnitude *more than reducing the size of the hash*.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-04-24 15:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-21 13:35 Why SHA are 40 bytes? (aka looking for flames) Marco Costalba
2007-04-21 15:08 ` Andy Parkins
2007-04-21 16:53 ` Karl Hasselström
2007-04-21 17:09 ` Marco Costalba
2007-04-21 16:58 ` Marco Costalba
2007-04-21 15:37 ` Jon Smirl
2007-04-21 17:06 ` Marco Costalba
2007-04-21 17:59 ` Jon Smirl
2007-04-21 18:28 ` Marco Costalba
2007-04-21 19:36 ` Jon Smirl
2007-04-24 14:48 ` Andreas Ericsson
2007-04-24 15:04 ` Nicolas Pitre
2007-04-24 15:18 ` Andreas Ericsson [this message]
2007-04-24 16:19 ` Nicolas Pitre
2007-04-22 13:27 ` Nicolas Pitre
2007-04-24 0:46 ` H. Peter Anvin
2007-04-24 2:30 ` Shawn O. Pearce
2007-04-24 2:44 ` Nicolas Pitre
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=462E1FBA.9020109@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=mcostalba@gmail.com \
--cc=nico@cam.org \
/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).