From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: oprofile on svn import
Date: Wed, 14 Jun 2006 21:38:09 +0200 [thread overview]
Message-ID: <e6poil$e8l$1@sea.gmane.org> (raw)
In-Reply-To: 9e4733910606141225n11b406fte6229ea9993825dd@mail.gmail.com
Jon Smirl wrote:
> Stats after 18 hours into git-svnimport. Process is now stuck in the
> kernel 64% of the time. All of the kernel time is in page management.
> Perl svnimport process is 290MB now.
>
> My top candidates for causing the problem are the fork in the perl
> code or the execing of a million tiny git processes.
>
> The key low level git functions could be made into a library to avoid
> the need to exec them continuously. The svn functions are libraries
> and they hardly show up.
There is ongoing effort to translate git functions into builtins.
Still you would need to translate git-svnimport Perl code into C,
or somehow access git library from Perl.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-06-14 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 1:10 oprofile on svn import Jon Smirl
2006-06-14 2:01 ` Eric Wong
2006-06-14 2:39 ` Jon Smirl
2006-06-14 3:02 ` Eric Wong
2006-06-14 4:48 ` Ryan Anderson
2006-06-14 5:26 ` Jon Smirl
2006-06-14 2:32 ` Jon Smirl
2006-06-14 19:25 ` Jon Smirl
2006-06-14 19:38 ` Jakub Narebski [this message]
2006-06-14 3:32 ` Martin Langhoff
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='e6poil$e8l$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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).