From: Sam Vilain <sam@vilain.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nicolas Pitre <nico@cam.org>,
Pierre Habouzit <madcoder@debian.org>,
Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Marco Costalba <mcostalba@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: Decompression speed: zip vs lzo
Date: Fri, 11 Jan 2008 14:01:01 +1300 [thread overview]
Message-ID: <4786BFCD.1000303@vilain.net> (raw)
In-Reply-To: <alpine.LFD.1.00.0801101454440.3148@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> On Fri, 11 Jan 2008, Sam Vilain wrote:
>> Drat, guess that means I'll have to recompute the deltas - I was trying
>> to avoid that.
>
> Well, you could try to reuse the delta base information itself, but then
> recompute the actual delta data contents. It would require some
> source-code changes, but that may be faster (and result in a more accurate
> before/after picture) than actually recomputing the deltas.
Yes, it would - but my runs have finished.
Without compression of deltas:
wilber:~/src/perl-preview$ git-repack -a -d -f --window=250 --depth=100
Compressing objects: 100% (236554/236554), done.
Writing objects: 100% (244360/244360), done.
Total 244360 (delta 182343), reused 0 (delta 0)
wilber:~/src/perl-preview$ du -sk .git/objects/pack/
86781 .git/objects/pack/
With compression of deltas:
wilber:~/src/perl-preview$ time git-repack -a -d -f --window=250 --depth=100
Counting objects: 244360, done.
Compressing objects: 100% (236554/236554), done.
Writing objects: 100% (244360/244360), done.
Total 244360 (delta 182343), reused 0 (delta 0)
real 20m34.985s
user 20m1.003s
sys 0m25.558s
wilber:~/src/perl-preview$ du -sk .git/objects/pack/
72907 .git/objects/pack/
wilber:~/src/perl-preview$ git --version
git version 1.5.4.rc2.7.g079c9-dirty
Of course those compression parameters are quite insane.
And as a side note either repack-objects got significantly better about
memory use between 1.5.3.5 and that version (the OOM killer fired -
killing first firefox and thunderbird :)) or apparently running
git-repack with a ulimit stops it from allocating too much VM.
Sam.
next prev parent reply other threads:[~2008-01-11 1:01 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
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 [this message]
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=4786BFCD.1000303@vilain.net \
--to=sam@vilain.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=madcoder@debian.org \
--cc=mcostalba@gmail.com \
--cc=nico@cam.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.