From: Linus Torvalds <torvalds@osdl.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: "linux@horizon.com" <linux@horizon.com>, git@vger.kernel.org
Subject: Re: svn to git, N-squared?
Date: Mon, 12 Jun 2006 09:12:16 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606120906210.5498@g5.osdl.org> (raw)
In-Reply-To: <9e4733910606120855p1cec9acfy62dadb89c11756b4@mail.gmail.com>
On Mon, 12 Jun 2006, Jon Smirl wrote:
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 14525 jonsmirl 16 0 604m 391m 1904 S 24 38.7 916:53.39 git-svnimport
> 20947 jonsmirl 17 0 0 0 0 R 1 0.0 0:00.03 git-svnimport
Hard to tell, it's obviously got short-lived processes there too that it's
not showing, but equally obviously that svnimport script itself is
spending an alarming amount of CPU time. I don't think it should do that
much processing, but since it's written in perl, I can't read it.
Are there any other directories that seem to be growing (eg some temp-file
directory where the old files aren't cleaned away?). I can't imagine what
else it could be doing in kernel space than simply some silly filesystem
operation, but dang it all, Linux filesystems are usually very efficient
indeed, unless we're talking huge directories (and if it's not the git
object directory any more, it must be something else).
At least with the cvs importer I have _some_ clue what it's doing, since I
wrote an earlier version myself (very different, but at least I know what
the operations are). SVN has always just confused me, and I have no idea
what svnimport does, so I think I'll have to defer to somebody who
actually knows the code.
Smurf, have you looked at any larger repositories?
Linus
next prev parent reply other threads:[~2006-06-12 16:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 4:39 svn to git, N-squared? linux
2006-06-12 15:32 ` Jon Smirl
2006-06-12 15:45 ` Linus Torvalds
2006-06-12 15:55 ` Jon Smirl
2006-06-12 16:12 ` Linus Torvalds [this message]
2006-06-12 16:22 ` Jon Smirl
2006-06-12 16:32 ` Jon Smirl
2006-06-12 16:57 ` Linus Torvalds
2006-06-12 16:41 ` Linus Torvalds
2006-06-12 16:44 ` Jon Smirl
2006-06-12 17:08 ` Linus Torvalds
2006-06-12 18:06 ` Jon Smirl
2006-06-12 19:00 ` Jon Smirl
2006-06-12 16:16 ` Jon Smirl
-- strict thread matches above, loose matches on Subject: below --
2006-06-12 2:02 Jon Smirl
2006-06-12 3:31 ` Linus Torvalds
2006-06-12 3:39 ` Jon Smirl
2006-06-12 4:02 ` Linus Torvalds
2006-06-12 19:04 ` Yakov Lerner
2006-06-12 19:17 ` Linus Torvalds
2006-06-12 16:18 ` Randal L. Schwartz
2006-06-12 16:25 ` Randal L. Schwartz
2006-06-12 4:29 ` Eric Wong
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=Pine.LNX.4.64.0606120906210.5498@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=linux@horizon.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).