From: Shawn Pearce <spearce@spearce.org>
To: git@vger.kernel.org
Cc: Jon Smirl <jonsmirl@gmail.com>
Subject: Re: Packfile can't be mapped
Date: Tue, 29 Aug 2006 01:33:12 -0400 [thread overview]
Message-ID: <20060829053312.GB24594@spearce.org> (raw)
In-Reply-To: <20060829045239.GB24479@spearce.org>
Shawn Pearce <spearce@spearce.org> wrote:
> This tree delta version came out pretty good. The pack with tree
> deltas is 874 MiB. Quite a reduction in size. fast-import takes
> about 20 minutes to convert its 20 GiB input file into this 874 MiB
> pack. Producing the 20 GiB input file from the 3 GiB CVS ,v
> files takes about 4 hours with Jon's modified cvs2svn.
>
> Jon has started a `git-repack -a -f` with aggressive depth and
> window sizes. He estimated it may need another 2.5 hours to process.
> Hopefully I'll hear more details tomorrow.
I just heard from Jon:
> git-repack -a -f --window=50 --depth=5000
> 100% CPU for 60 minutes
> 1.2GB resident memory
> Final pack size is 451,203,363 bytes.
So with very agressive delta depth and window sizes git-repack took
a while to run but came very close to the best packed size from
previous Mozilla CVS import attempts. I think we'd still like to
make the final historical pack smaller than that.
--
Shawn.
prev parent reply other threads:[~2006-08-29 5:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 1:04 Packfile can't be mapped Jon Smirl
2006-08-28 2:47 ` Shawn Pearce
2006-08-28 4:27 ` Nicolas Pitre
2006-08-28 4:36 ` Linus Torvalds
2006-08-28 6:00 ` Shawn Pearce
2006-08-28 14:15 ` Jon Smirl
2006-08-28 14:40 ` Nicolas Pitre
2006-08-28 15:44 ` Jon Smirl
2006-08-28 16:43 ` Nicolas Pitre
2006-08-28 16:48 ` Shawn Pearce
2006-08-28 14:48 ` Nicolas Pitre
2006-08-28 5:33 ` Shawn Pearce
2006-08-28 16:42 ` Shawn Pearce
2006-08-28 17:19 ` Nicolas Pitre
2006-08-29 4:52 ` Shawn Pearce
2006-08-29 5:33 ` Shawn Pearce [this message]
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=20060829053312.GB24594@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@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).