git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: "Lukas Sandström" <lukass@etek.chalmers.se>
Cc: git@vger.kernel.org, junkio@cox.net
Subject: Re: [PATCH] Make git-pack-redundant non-horribly slow on large sets of packs
Date: Thu, 17 Nov 2005 21:39:15 +0100	[thread overview]
Message-ID: <20051117203915.GB3013@steel.home> (raw)
In-Reply-To: <81b0412b0511162345g1483e7cfia768b18ba3eb1db@mail.gmail.com> <437C819C.4040507@etek.chalmers.se>

Lukas Sandström, Thu, Nov 17, 2005 14:11:56 +0100:
> Change the smallest-set detection algortithm so that when
> we have found a good set, we don't check any larger sets.

I used latest git (a575603af20a795584d79b32c30bda10fcae5d3f Merge
branch 'tojunio' of http://locke.catalyst.net.nz/git/git-martinlanghoff)
and the patch on top.

Alex Riesen, Thu, Nov 17, 2005 08:45:46 +0100:
> > Could you try updating to the latest snapshot? There was a bug in a
> > list handling function which was fixed recently, perhaps your problem
> > is related.
> 
> will try, but I didn't realize yesterday that it might be a good idea
> to keep the old repository around. The lot of packs was automatically
> created by incremental repacking after every pull. Sorry...

ok, pack-redundant --all in a repository with 25 packs completed in
1.346 sec. That's definitely an improvement.

But, the repository (a clone of Linus' kernel) didn't have a
superpack. I created one (git repack -a) and started
"pack-redundant --all". And almost oomed the system (it has 1Gb RAM +
512Mb(historically) swap, BTW): oom-killer killed git-pack-redundant.
Peak memory usage was around 1.3Gb, than everything stopped. The
repository had 140718 objects.

  reply	other threads:[~2005-11-17 20:39 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-17  7:45   ` Alex Riesen
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
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 [this message]
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

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=20051117203915.GB3013@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=lukass@etek.chalmers.se \
    /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).