From: Shawn Pearce <spearce@spearce.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>, Nicolas Pitre <nico@cam.org>
Subject: Re: 1.3.0 creating bigger packs than 1.2.3
Date: Thu, 20 Apr 2006 13:55:54 -0400 [thread overview]
Message-ID: <20060420175554.GH31738@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0604200954440.3701@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
> Ok, so that wasn't it, and the new sort order is superior.
>
> That means that it probably _is_ the delta changes themselves (probably
> commit c13c6bf7 "diff-delta: bound hash list length to avoid O(m*n)
> behavior". You can try
>
> git revert c13c6bf7
No effect.
> to see if that's it. Although Nico already showed interest, and if you
> make the archive available to him, he's sure to figure it out.
I sent the URL privately to Nico as I did not want the repository
to be publically available before next Tuesday.
> You can try "--depth=50" (slogan: more "hot delta on delta action"), but
> it's looking less and less like a delta selection issue, and more and more
> like the deltas themselves are deproved.
No effect at either 50 or 100.
The more that I think about it the more it seems possible that the
pathname hashing is what may be causing the problem. Not only did
bisect point to 1d6b38cc76c348e2477506ca9759fc241e3d0d46 but the
directory which contains the bulk of the space has many files with
the same name located in different directories:
results/MT/Math/10000/0-11-AdjLite.deg
results/MT/Math/10000/0-12-AdjLite.deg
...
results/MT/Math/30000/2-11-AdjLite.deg
results/MT/Math/30000/2-12-AdjLite.deg
...
results/Rand48/Math/10000/2-11-AdjLite.deg
results/Rand48/Math/10000/2-12-AdjLite.deg
...
results/Rand48/Math/30000/2-11-AdjLite.deg
results/Rand48/Math/30000/2-12-AdjLite.deg
...
For example the name '0-11-AdjLite.deg' occurs in 63 directories and
none of those occurrances are likely to delta against one another
very well. Also most of these files only have 1 or 2 revisions,
so there is very little per-file history.
--
Shawn.
next prev parent reply other threads:[~2006-04-20 17:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 13:36 1.3.0 creating bigger packs than 1.2.3 Shawn Pearce
2006-04-20 14:47 ` Linus Torvalds
2006-04-20 15:03 ` Shawn Pearce
2006-04-20 16:07 ` Linus Torvalds
2006-04-20 16:43 ` Shawn Pearce
2006-04-20 17:03 ` Linus Torvalds
2006-04-20 17:24 ` Junio C Hamano
2006-04-20 17:31 ` Shawn Pearce
2006-04-20 17:54 ` Nicolas Pitre
2006-04-20 21:31 ` Junio C Hamano
2006-04-20 21:53 ` Shawn Pearce
2006-04-20 21:56 ` Jakub Narebski
2006-04-20 17:41 ` Nicolas Pitre
2006-04-20 17:55 ` Shawn Pearce [this message]
2006-04-20 18:24 ` Nicolas Pitre
2006-04-20 18:49 ` Junio C Hamano
2006-04-20 21:02 ` Nicolas Pitre
2006-04-20 21:40 ` Junio C Hamano
2006-04-20 22:02 ` Shawn Pearce
2006-04-20 22:35 ` Junio C Hamano
2006-04-21 1:01 ` Shawn Pearce
2006-04-20 22:59 ` Linus Torvalds
2006-04-21 0:52 ` Nicolas Pitre
2006-04-21 1:20 ` Shawn Pearce
2006-04-21 2:28 ` Nicolas Pitre
2006-04-21 2:40 ` Shawn Pearce
2006-04-21 3:07 ` Nicolas Pitre
2006-04-21 2:32 ` Shawn Pearce
2006-04-20 23:02 ` Junio C Hamano
2006-04-20 16:09 ` 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=20060420175554.GH31738@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=torvalds@osdl.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).