public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student•ethz.ch>
To: Ken Brownfield <krb@irridia•com>
Cc: <git@vger•kernel.org>
Subject: Re: Performance issue exposed by git-filter-branch
Date: Fri, 17 Dec 2010 02:54:12 +0100	[thread overview]
Message-ID: <201012170254.13005.trast@student.ethz.ch> (raw)
In-Reply-To: <41C1B4AC-8427-4D62-BEB6-689A4BE4EE5B@irridia.com>

Ken Brownfield wrote:
> git filter-branch --index-filter 'git rm -r --cached --ignore-unmatch -- bigdirtree stuff/a stuff/b stuff/c stuff/dir/{a,b,c}' --prune-empty --tag-name-filter cat -- --all
[...]
> Now that the same repository has grown, this same filter-branch
> process now takes 6.5 *days* at 100% CPU on the same machine (2x4
> Xeon, x86_64) on git-1.7.3.2.  There's no I/O, memory, or other
> resource contention.

If all you do is an index-filter for deletion, I think it should be
rather easy to achieve good results by filtering the fast-export
stream to remove these files, and then piping that back to
fast-import.

(It's just that AFAIK nobody has written that code yet.)

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  parent reply	other threads:[~2010-12-17  1:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-17  1:07 Performance issue exposed by git-filter-branch Ken Brownfield
2010-12-17  1:45 ` Jonathan Nieder
2010-12-17  2:31   ` Ken Brownfield
2010-12-17  3:22     ` Jonathan Nieder
2010-12-17  3:37       ` Jonathan Nieder
2010-12-17  1:54 ` Thomas Rast [this message]
2010-12-17  2:36   ` Ken Brownfield
2010-12-17  2:51     ` Jakub Narebski
2010-12-21  4:49       ` Ken Brownfield
2010-12-17  3:08     ` Jonathan Nieder
2010-12-17  5:39       ` Elijah Newren
2011-02-04 21:17         ` Ken Brownfield
2011-02-05 14:21           ` Elijah Newren
2010-12-17 13:01 ` Nguyen Thai Ngoc Duy
2010-12-21  4:59   ` Ken Brownfield

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=201012170254.13005.trast@student.ethz.ch \
    --to=trast@student$(echo .)ethz.ch \
    --cc=git@vger$(echo .)kernel.org \
    --cc=krb@irridia$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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