From: Theodore Tso <tytso@MIT.EDU>
To: "Fedor V. Sergeev" <theodor@geo.phys.spbu.ru>
Cc: git@vger.kernel.org
Subject: Re: hg-to-git performance on big repos
Date: Sat, 22 Mar 2008 10:27:58 -0400 [thread overview]
Message-ID: <20080322142758.GT7991@mit.edu> (raw)
In-Reply-To: <20080322162618.K47359@geo.geo.loc>
On Sat, Mar 22, 2008 at 04:34:22PM +0300, Fedor V. Sergeev wrote:
> Folks,
>
> I'm trying to convert a relatively big Mercurial repo (70K commits)
> into Git using contrib/hg-to-git. It initially goes fine but starts
> to slow down nearly exponentially as the number of converted
> changesets goes up.
>
> git-fast-import seems to just hang around, while all the work (100% cpu)
> is spent in that python thing. It does not eat up memory, pstack looks
> fine, but after some 10K commits it just crawls.
I don't know if it will be better, but at the time when I needed to
convert e2fsprogs, I liked the results of hg-fast-export, found at:
url = git://repo.or.cz/fast-export.git
You might hg-fast-import and see if it does any better for your repo.
Does it have a large number of branches or tags, by any chance?
- Ted
prev parent reply other threads:[~2008-03-22 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 13:34 hg-to-git performance on big repos Fedor V. Sergeev
2008-03-22 14:27 ` Theodore Tso [this message]
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=20080322142758.GT7991@mit.edu \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=theodor@geo.phys.spbu.ru \
/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).