git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henning Moll <newsScott@gmx.de>
To: git@vger.kernel.org
Subject: filter-branch performance
Date: Tue, 09 Dec 2014 19:52:33 +0100	[thread overview]
Message-ID: <548744F1.9000902@gmx.de> (raw)

Hi,

i am runningthis command

git filter-branch --env-filter 'export 
GIT_COMMITTER_EMAIL="$GIT_AUTHOR_EMAIL" 
GIT_COMMITTER_NAME="$GIT_AUTHOR_NAME" 
GIT_COMMITTER_DATE="$GIT_AUTHOR_DATE"' --prune-empty --tag-name-filter 
cat -- --all


in a repository which i copied to /dev/shm before. According to "top", 
the git process only consumes about 5 percent of the CPU. The load is 
between 0.70 and 1.00.

I assume that there is a lot of process forking going on. Could that be 
the cause?

Any ideas how to further improve?

Best regards
Henning

             reply	other threads:[~2014-12-09 18:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09 18:52 Henning Moll [this message]
2014-12-09 18:59 ` filter-branch performance Jeff King
2014-12-10 14:18   ` Roberto Tyley
2014-12-10 14:37     ` Jeff King
2014-12-10 15:25       ` Roberto Tyley
2014-12-10 16:05     ` Junio C Hamano
2014-12-10 23:44       ` Roberto Tyley

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=548744F1.9000902@gmx.de \
    --to=newsscott@gmx.de \
    --cc=git@vger.kernel.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).