git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bdowning@lavos.net (Brian Downing)
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: [BUG] fast-import producing very deep tree deltas
Date: Mon, 12 Nov 2007 05:03:56 -0600	[thread overview]
Message-ID: <20071112110354.GP6212@lavos.net> (raw)

I've happened upon a case where fast-import produces deep tree deltas.
How deep?  Really deep.  6035 entries deep to be precise for this case:

    depths: count 135970 total 120567366 min 0 max 6035 mean 886.72 median 3 std_dev 1653.48

    27b8a20bdf39fecd917e8401d3499013e49449d0 tree   32 99609547 6035 0000000000000000000000000000000000000000

This was with git-fast-import from 'next' as of a couple days ago,
run with the default options (no --depth passed in).

Needless to say the pack that resulted was just about useless.  Trying to
repack it resulted in the "counting objects" phase running at about five
objects per second.

I don't know much about the fast-import code, but I'd guess that the
delta_depth member for the tree_content struct is either getting cleared
inappropriately or is not being propagated correctly.  I added a printout
of the depth just before the store_object call in store_tree and it is
never non-zero, even though the pack file clearly was generated with
plenty of deltas.

I may have time to look at this more later this week, but I just wanted
it to be known that this problem existed.

-bcd

             reply	other threads:[~2007-11-12 11:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 11:03 Brian Downing [this message]
2007-11-12 11:13 ` [BUG] fast-import quoting broken for renames Brian Downing
2007-11-12 20:26 ` [BUG] fast-import producing very deep tree deltas Linus Torvalds
2007-11-13  8:53 ` Shawn O. Pearce
2007-11-13  9:27   ` Shawn O. Pearce
2007-11-13 14:36     ` Brian Downing

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=20071112110354.GP6212@lavos.net \
    --to=bdowning@lavos.net \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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).