git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lukas Sandström" <lukass@etek.chalmers.se>
To: git@vger.kernel.org
Cc: "Linus Torvalds" <torvalds@osdl.org>,
	"Alex Riesen" <raa.lkml@gmail.com>,
	junkio@cox.net, "Lukas Sandström" <lukass@etek.chalmers.se>
Subject: Re: fix git-pack-redundant crashing sometimes
Date: Wed, 16 Nov 2005 22:37:42 +0100	[thread overview]
Message-ID: <437BA6A6.8080900@etek.chalmers.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0511151552400.11232@g5.osdl.org>

Linus Torvalds wrote:
> 
> On Tue, 15 Nov 2005, Alex Riesen wrote:
> 
>>Sorry, it doesn't. The code loops here:
>>
>>401             /* find the permutations which contain all missing objects */
>>402             perm_all = perm = get_all_permutations(non_unique);
> 
> 
> Looks like the whole thing is exponential.
> 
Slightly less, but not far from.
> A good way to do sane pack handling is to keep a _sorted_ list of all 
> objects each pack has. At that point it becomes much easier to see which 
> objects only exist in one particular pack.
> 
git-pack-redundant already does this.
> The sorting itself is O(nlogn), and the "does this pack have any unique 
> objects" (or "is this pack a superset of all other packs") question should 
> then be O(n).
> 
Ah, but the question is: "Does this set of packs contain a superset of
all objects available in packfiles?" The answer to the question for a
certain set is indeed O(n), but the number of sets which have to be tested
are ~ O(e**n). (Where n is the number of non-unique packs.)

/Lukas

  parent reply	other threads:[~2005-11-16 21:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 23:09 git-pack-redundant returns the most containing pack Alex Riesen
2005-11-16 23:23 ` Lukas Sandström
2005-11-15 15:49   ` fix git-pack-redundant crashing sometimes Alex Riesen
2005-11-15 16:08     ` Timo Hirvonen
2005-11-15 16:11       ` Alex Riesen
2005-11-15 17:28         ` Linus Torvalds
2005-11-15 21:38       ` Lukas Sandström
2005-11-15 21:24     ` [PATCH] Fix llist_sorted_difference_inplace in git-pack-redundant Lukas Sandström
2005-11-15 21:34     ` fix git-pack-redundant crashing sometimes Alex Riesen
2005-11-15 21:41       ` Lukas Sandström
2005-11-15 22:33         ` Alex Riesen
2005-11-15 23:13           ` Lukas Sandström
2005-11-16  7:01             ` Alex Riesen
2005-11-16 21:11             ` Alex Riesen
2005-11-15 23:58           ` Linus Torvalds
2005-11-16 20:13             ` Junio C Hamano
2005-11-16 21:37             ` Lukas Sandström [this message]
2005-11-16 23:59               ` Lukas Sandström
2005-11-17 16:56                 ` Matthias Urlichs
2005-11-17  7:08               ` Fredrik Kuivinen
2005-11-17 13:11           ` [PATCH] Make git-pack-redundant non-horribly slow on large sets of packs Lukas Sandström
2005-11-17 20:39             ` Alex Riesen
2005-11-18 16:30             ` [PATCH] Fix bug introduced by the latest changes to git-pack-redundant Lukas Sandström
2005-11-18 21:53             ` [PATCH] Fix a bug in get_all_permutations Lukas Sandström
2005-11-17  7:45   ` git-pack-redundant returns the most containing pack Alex Riesen

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=437BA6A6.8080900@etek.chalmers.se \
    --to=lukass@etek.chalmers.se \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=raa.lkml@gmail.com \
    --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).