From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Eric Wong" <normalperson@yhbt.net>
Cc: git <git@vger.kernel.org>
Subject: Re: oprofile on svn import
Date: Tue, 13 Jun 2006 22:39:32 -0400 [thread overview]
Message-ID: <9e4733910606131939h35b2278bvaa296459ea061621@mail.gmail.com> (raw)
In-Reply-To: <20060614020108.GB12083@hand.yhbt.net>
On 6/13/06, Eric Wong <normalperson@yhbt.net> wrote:
> Jon Smirl <jonsmirl@gmail.com> wrote:
> > I'm going back to cvsimport tomorrow. My svn import that had been
> > running for five days got killed this morning when the city decided to
> > move the telephone pole that provides my electricty.
> >
> > Some oprofile data, this doesn't make a lot of sense to me. Why is it
> > in libcypto so much?
>
> The sha1 calculation is done in libcrypto, afaik.
That make sense, but it's eating up 14% of my CPU in a long sample.
> Anybody want to see how my latest patches to git-svn (and using SVN perl
> libraries) stacks up against the mozilla repo? Speedwise, I don't
> expect git-svn to be too different than git-svnimport, but it should use
> much less memory (I'll probably port the hacks to git-svnimport, too).
Can svnimport be rewritten to avoid calling fork? If I am reading the
oprofiles correctly that fork is very expensive especially when the
svnimport task grows to 600MB.
I have an import running but post your code when it is ready and I can
try it on the next run. They always seem to fail so there will
probably be another run.
> I'll see about freeing up one of my machines to test the mozilla repo.
> Unfortunately, all of my hardware is a few years old and not extremely
> fast.
>
> --
> Eric Wong
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2006-06-14 2:39 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 [this message]
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
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=9e4733910606131939h35b2278bvaa296459ea061621@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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).