git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Ken Brownfield <krb@irridia.com>
Cc: git@vger.kernel.org, David Barr <david.barr@cordelta.com>
Subject: Re: Performance issue exposed by git-filter-branch
Date: Thu, 16 Dec 2010 19:45:39 -0600	[thread overview]
Message-ID: <20101217014539.GA6775@burratino> (raw)
In-Reply-To: <41C1B4AC-8427-4D62-BEB6-689A4BE4EE5B@irridia.com>

Hi Ken,

Ken Brownfield wrote:

> Is there a way to apply the optimizations mentioned in that old
> thread to the code paths used by git-filter-branch (mainly git-read
> and git-rm, seemingly), or is there another way to investigate and
> improve the performance of the filter?

Which old thread?

You might be able to get faster results using the approach of [1]
(using "git cat-file --batch-check" to collect the trees you want
and "git fast-import" to paste them together), which avoids unpacking
trees when not needed.

Hope that helps,
Jonathan

[1] http://repo.or.cz/w/git/barrbrain/github.git/commitdiff/db-svn-filter-root

  reply	other threads:[~2010-12-17  1:46 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 [this message]
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
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=20101217014539.GA6775@burratino \
    --to=jrnieder@gmail.com \
    --cc=david.barr@cordelta.com \
    --cc=git@vger.kernel.org \
    --cc=krb@irridia.com \
    /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).